zalando-incubator / zalando-incubator/stackset-controller
pre define shunt backend in case routegroups are used
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 183
- Forks
- 29
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 5
Description
I am not sure if it makes sense, but a user had the idea to pre define shunt backend in case routegroups are used, such that they don't need to define additionalBackends. I documented additionalBackends now in https://github.com/zalando-incubator/stackset-controller/pull/288
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
Review the issue proposal and PR #288, which documents additionalBackends. Trace how routegroups and additionalBackends are currently handled in the controller, then clarify whether a shunt backend should be predefined. Done should include an agreed behavior and acceptance checks for routegroups without additionalBackends.
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
- 25/100