zalando-incubator / zalando-incubator/stackset-controller
Traffic to failed init stackset deployment
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 183
- Forks
- 29
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 5
Description
When I deploy for the first time and my stackset is broken in someway (e.g. typo in the image name) desired traffic is set to 100% on that initial stack. Subsequent successful deployments will have actual traffic evenly distributed among them.
Is this actually the desired behavior?
I would expect 100% traffic assigned to the very first successful deployment.
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 tracing the StackSet controller's traffic handling for an initial deployment that fails, using the reported broken image-name scenario to reproduce it. Verify that a failed initial deployment does not receive 100% traffic and that the first successful deployment receives 100% traffic before later deployments are distributed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100