zalando-incubator / zalando-incubator/stackset-controller
All-zero weights: is it allowed and how is traffic distributed
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 183
- Forks
- 29
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 5
Description
There is unclarity how an all-zero traffic weight is handled and interpreted.
Handled (currently):
- rejected by at least one client (zkubectl)
- Not handled by the server (stackset controller allows this setting)
Interpretation (currently)
- stackset-controller resolves all-zero weights to equal traffic distribution
- this seems undesireable by a majority of users at the moment
Clarify what's the desired behaviour:
- Should all-zero weights be possible at all
- where to make the validation and reject the request?
- How to interpret all-zero weights if allowed
- equal distribution or zero traffic
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 with the issue's description of all-zero weights, comparing validation in zkubectl with handling in the stackset controller. Determine the intended behavior for rejecting all-zero requests and for traffic interpretation, then document the decision and its validation point; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100