cloudfoundry / cloudfoundry/stratos
Ability to set number of replicas for rolling deploy
Open
Nobody has claimed this yet.
community
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
Stratos Version
4.3.0
Frontend Deployment type
- Cloud Foundry Application (cf push)
- Kubernetes, using a helm chart
- Docker, single container deploying all components
- npm run start
- Other (please specify below)
Backend (Jet Stream) Deployment type
- Cloud Foundry Application (cf push)
- Kubernetes, using a helm chart
- Docker, single container deploying all components
- Other (please specify below)
Expected behaviour
Stratos should be able to have a configuration update helm upgrade ... without downtime. This would involve configuring rolling deploys and allowing more than 1 replica.
Actual behaviour
Stratos will go offline and be unreachable if you helm upgrade ...
Steps to reproduce the behavior
- Deploy Stratos using Helm
- Update the Stratos config with
helm upgrade ...
Notice Stratos goes offline
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 locating the Helm chart used for the Kubernetes deployment and inspect its deployment configuration. Reproduce the issue with a helm upgrade, then verify that configuration updates keep Stratos reachable while allowing more than one replica and a rolling deployment.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100