-
Notifications
You must be signed in to change notification settings - Fork 8
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
base: main
Are you sure you want to change the base?
feat: Add support for topologySpreadConstraints #273
Conversation
d05cdf8
to
91f8bd6
Compare
91f8bd6
to
473b509
Compare
There was a problem hiding this 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?
There was a problem hiding this 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
charts/operator-wandb/charts/otel/charts/agent/templates/deamonset.yaml
Outdated
Show resolved
Hide resolved
53c8d1f
to
db5c8d6
Compare
925acd3
to
10a0c21
Compare
No description provided.