somaz94 opened a new pull request, #11917: URL: https://github.com/apache/gravitino/pull/11917
### What changes were proposed in this pull request? Add an opt-in `topologySpreadConstraints` value to the Gravitino, Iceberg REST, and Lance REST Helm charts. It defaults to `[]` (no change to existing deployments) and is written into each Deployment's pod spec alongside the existing `affinity` / `tolerations` fields. ### Why are the changes needed? Enterprises running on multi-AZ Kubernetes clusters often require workloads to be spread across zones or nodes for HA. Without this field, all pods of a chart can land on the same node/AZ, creating a single point of failure. Fix: #10864 ### Does this PR introduce _any_ user-facing change? Yes, a new optional `topologySpreadConstraints` value (default `[]`) in all three charts. No behavior change when unset. ### How was this patch tested? helm unittest on all three charts (added a render test per chart; iceberg/lance also assert the field is absent by default): - gravitino: 38 passed - gravitino-iceberg-rest-server: 33 passed - gravitino-lance-rest-server: 32 passed Also verified with helm lint and helm template that the constraints render into the pod spec when set and are omitted when unset. -- 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]
