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 support for topologySpreadConstraints #2563

Closed
BryanStenson-okta opened this issue Mar 18, 2022 · 1 comment
Closed

add support for topologySpreadConstraints #2563

BryanStenson-okta opened this issue Mar 18, 2022 · 1 comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.

Comments

@BryanStenson-okta
Copy link

BryanStenson-okta commented Mar 18, 2022 •
edited

Is your feature request related to a problem?
Specifically, I'm trying to use karpenter to schedule nodes on demand, and it uses topologySpreadConstraints

This chart doesn't support these constraints.

Describe the solution you'd like
I'd like the helm chart to support optional topologySpreadConstraints if set in the values.yaml. If omitted, it should do nothing.

Describe alternatives you've considered
@kishorj kishorj added the good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. label Mar 19, 2022
@BryanStenson-okta
Copy link
Author

BryanStenson-okta commented Mar 21, 2022 •
edited

splitting the affinity default debacle into another issue here: #2570

@BryanStenson-okta BryanStenson-okta changed the title add support for topologySpreadConstraints, more sane affinity default add support for topologySpreadConstraints Mar 21, 2022
@BryanStenson-okta BryanStenson-okta mentioned this issue Mar 21, 2022
Closed
6 tasks
@stensonb stensonb mentioned this issue Mar 22, 2022
Merged
6 tasks
@kishorj kishorj closed this as completed Mar 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kishorj @BryanStenson-okta