younsl opened a new pull request, #213: URL: https://github.com/apache/superset-kubernetes-operator/pull/213
## Summary Add an optional `topologySpreadConstraints` value to the operator Helm chart so users can control how manager pods are distributed across failure domains such as nodes and zones. The chart already exposed `nodeSelector`, `affinity`, and `tolerations`, but had no first-class way to configure [topology spread](https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/), forcing users to approximate it with affinity rules for a scheduling concern Kubernetes models natively. This is most useful when running more than one replica for high availability. ## Details The value defaults to an empty list, so the [`topologySpreadConstraints`](https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/) field is omitted from the rendered [Deployment](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) unless set, preserving existing behavior. Changes span the four places the chart tracks a pod-scheduling value: - `templates/deployment.yaml` renders the block after [`tolerations`](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/) via the standard `with` guard - `values.yaml` documents the new key with an empty-list default - `values.schema.json` types it as an array - `README.md` is regenerated via helm-docs to match Each constraint follows the standard [`TopologySpreadConstraint`](https://pkg.go.dev/k8s.io/api/core/v1#TopologySpreadConstraint) shape (`maxSkew`, `topologyKey`, `whenUnsatisfiable`, `labelSelector`). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
