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

feat: Add support for topologySpreadConstraints #273

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

velotioaastha
Copy link
Contributor

No description provided.

@velotioaastha velotioaastha changed the title featadd support for topologyspreadconstraints feat: Add support for topologySpreadConstraints #308 Dec 3, 2024
@velotioaastha velotioaastha changed the title feat: Add support for topologySpreadConstraints #308 feat: Add support for topologySpreadConstraints Dec 3, 2024
@velotioaastha velotioaastha force-pushed the aastha/add-support-for-topologyspreadconstraints branch from d05cdf8 to 91f8bd6 Compare December 4, 2024 13:46
@velotioaastha velotioaastha force-pushed the aastha/add-support-for-topologyspreadconstraints branch from 91f8bd6 to 473b509 Compare December 5, 2024 05:47
@abhinavg6 abhinavg6 requested a review from theishshah December 9, 2024 16:37
Copy link
Contributor

@theishshah theishshah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The addition of the topology flags looks good to me, are there any modules where we would want to enable this or just keeping it optional and false for now?

Copy link
Contributor

@danielpanzella danielpanzella left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

redis-exporter, mysql-exporter, stackdriver, and prometheus are going to be run as single instances so not sure adding topology constraints makes any sense. I'm not sure we should be applying these to things like mysql or redis either. so probably just dont include this for any of the non-application deployments

@velotioaastha velotioaastha force-pushed the aastha/add-support-for-topologyspreadconstraints branch from 53c8d1f to db5c8d6 Compare December 18, 2024 12:49
@velotioaastha velotioaastha force-pushed the aastha/add-support-for-topologyspreadconstraints branch from 925acd3 to 10a0c21 Compare December 18, 2024 13:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Feature Request | Add support for topologySpreadConstraints
3 participants