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.

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

[helm chart] Include optional "topologySpreadConstraints" in defaultbackend #11194

Closed
peterabarr opened this issue Apr 3, 2024 · 1 comment · Fixed by #11197
Closed

[helm chart] Include optional "topologySpreadConstraints" in defaultbackend #11194

peterabarr opened this issue Apr 3, 2024 · 1 comment · Fixed by #11197
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@peterabarr
Copy link

peterabarr commented Apr 3, 2024

What do you want to happen?
Being able to set topologySpreadConstraints in the defaultbackend like in the controller.

Is there currently another issue associated with this?
Not that I could see.

Does it require a particular kubernetes version?
Minimum v1.27.

@peterabarr peterabarr added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 3, 2024
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Apr 3, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Development

Successfully merging a pull request may close this issue.

2 participants