Feature: Set NC_serverid per instance
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 534
- Forks
- 314
- Avg merge
- 42m
- Merged PRs (30d)
- 1
Description
Description of the change
Since NC 33 the UI recommends setting NC_serverid to a unique value per server of a nextcloud cluster. Since the ids should be stable and unique it suggests using a StatefulSet and using its ordinal as the serverid value.
Benefits
Not sure what the actual benefit is, but since NC suggests/recommends it, I guess the chart should comply.
Possible drawbacks
No idea if setting NC_serverid has drawbacks, but switching to a StatefulSet does make things a little more complicated.
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 reading the chart's current workload definition and the Nextcloud serverid documentation linked in the issue. Determine how a StatefulSet ordinal can provide a stable, unique NC_serverid for each instance without breaking existing deployments. Done means the chart supports per-instance server IDs and its rendered Kubernetes resources reflect the intended StatefulSet behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100