nuts-foundation / nuts-foundation/nuts-node
Kubernetes: upgrades and scaling (with bbolt)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 28
- Forks
- 23
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 76
Description
Please correct me if I'm wrong but right now only bbolt is supported for at least some of the data that is stored in the Nuts Node. Even when SQL storage is configured. This has a couple of downsides:
- Upgrades; Zero-downtime upgrades are impossible since there can only be one instance.
- High-availability; Not supported since there can only be one instance.
Right now you can configure replicas and/or autoscaling but both won't work (due to the issues above). It would be better to switch from a Deployment to a StatefulSet with a static replica of 1.
Contributor guide
No contributing guide indexed for this repository
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 tracing the Nuts Node's bbolt usage and reviewing the Kubernetes Deployment configuration, including replicas and autoscaling. Confirm whether bbolt requires a single instance, then assess the requested StatefulSet with a static replica of 1 and verify that the resulting configuration matches the storage constraints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- databases, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100