install from helm repo
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 534
- Forks
- 314
- Avg merge
- 42m
- Merged PRs (30d)
- 1
Description
Describe your Issue
i did a fresh install of next cloud from helm repo
after when i create a new use and it seems to goes the thinstall and after the install i get Service Unavailable
Logs and Errors
Describe your Environment
-
Kubernetes distribution: k3s
-
Helm Version (or App that manages helm):
-
Helm Chart Version: https://nextcloud.github.io/helm/ nextcloud-4.5.12
-
values.yaml:
cronjob:
annotations: {}
curlInsecure: false
enabled: true
failedJobsHistoryLimit: 5
image: {}
schedule: '*/5 * * * *'
successfulJobsHistoryLimit: 2
hpa:
enabled: false
image:
repository: nextcloud
tag: 27-apache
pullPolicy: IfNotPresent
internalDatabase:
enabled: false
mariadb:
db:
name: nextcloud
password: db-password
user: nextcloud
enabled: true
master:
persistence:
accessMode: ReadWriteOnce
enabled: true
size: 8Gi
replication:
enabled: false
rootUser:
password: root-db-password
forcePassword: true
postgresql:
enabled: false
metrics:
enabled: false
defaultConfigs:
.htaccess: true
apache-pretty-urls.config.php: true
apcu.config.php: true
apps.config.php: true
autoconfig.php: true
redis.config.php: true
smtp.config.php: false
persistence:
accessMode: ReadWriteOnce
annotations: {}
enabled: true
size: 8Gi
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing a fresh install of chart version 4.5.12 on k3s with the supplied values.yaml, then collect the Nextcloud and related pod logs around user creation. Determine why the deployment returns Service Unavailable after installation; done means the cause is documented and a verified chart or configuration fix prevents the failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, mariadb
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100