add support for Pod Topology Spread Constraints to the linkerd Deployment objects & Helm charts
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
### What problem are you trying to solve?
Pod Topology Spread Constraints enable the configuration of deployments to be spread across failure-domains (e.g., AWS Availability Zones). Some users would like to be able to enable such a feature for Linkerd out of the box, both for consistency with workloads in those clusters, as well as part of their fault tolerance posture.
Link to documentation: https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/
### How should the problem be solved?
Add feature to helm chart and deployment templates
### Any alternatives you've considered?
n/a
### How would users interact with this feature?
Helm
### Would you like to work on this feature?
None
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
Locate the Linkerd Helm charts and deployment templates referenced by the issue, then read the Kubernetes topology spread constraints documentation linked in the report. Verify how Helm values reach the rendered Deployment objects; done means users can configure the constraints through Helm and the resulting deployments include them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100