You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered: