Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add topologySpreadConstraints to Flagger helm chart #1765

Open
frittentheke opened this issue Feb 20, 2025 · 0 comments · May be fixed by #1766
Open

Add topologySpreadConstraints to Flagger helm chart #1765

frittentheke opened this issue Feb 20, 2025 · 0 comments · May be fixed by #1766

Comments

@frittentheke
Copy link

Describe the feature

Allow setting topologySpreadConstraints (https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/)
in the flagger Helm chart.

This is just like the spec.deployment.affinity setting allowing to further configure the pod placement.

Proposed solution

Add a parameter topologySpreadConstraints to the values and reference it is the deployment template.

Any alternatives you've considered?
frittentheke added a commit to frittentheke/flagger that referenced this issue Feb 20, 2025
@frittentheke
Allow configuration of topologySpreadConstraints for flagger deployment
5a29a7f 
Resolves: fluxcd#1765
@frittentheke frittentheke linked a pull request Feb 20, 2025 that will close this issue
Open
frittentheke added a commit to frittentheke/flagger that referenced this issue Feb 20, 2025
@frittentheke
Allow configuration of topologySpreadConstraints for flagger deployment
ee5633c 
Resolves: fluxcd#1765
Signed-off-by: Christian Rohmann <christian.rohmann@inovex.de>
frittentheke added a commit to frittentheke/flagger that referenced this issue Feb 20, 2025
@frittentheke
Allow configuration of topologySpreadConstraints for flagger deployment
a2d4149 
Resolves: fluxcd#1765
Signed-off-by: Christian Rohmann <christian.rohmann@inovex.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Allow configuration of topologySpreadConstraints for flagger deployment frittentheke/flagger
1 participant
@frittentheke