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

Brokers should be deployed to different AZ, we better add topology spread contstraint #521

Open
wangshu3000 opened this issue Aug 21, 2024 · 0 comments · May be fixed by #526
Open

Brokers should be deployed to different AZ, we better add topology spread contstraint #521

wangshu3000 opened this issue Aug 21, 2024 · 0 comments · May be fixed by #526

Comments

@wangshu3000
Copy link
Contributor

Is your feature request related to a problem? Please describe.
I see broker sts doesn't support topology constraint configuration. That means 2 pods in the sts may possible depoyed to on az in kubernetes cluster.

Describe the solution you'd like
We can add a topology spread constraint configuration to deployed the pods in sts spread to different az, so that under an AZ outage, the impact can be only limited to small number of brokers.

Additional context
Reference about topology spread constraint: https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

If it make sense, i can raise a PR to add it.

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant