-
Notifications
You must be signed in to change notification settings - Fork 43
Add optional AZ awareness topology constraints #176
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -74,6 +74,14 @@ volumeMounts: [] | |
| # -- Configure [topology spread constraints](https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/). | ||
| topologySpreadConstraints: [] | ||
|
|
||
| # Availability Zone awareness | ||
| azAwareness: | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I’d prefer not to introduce a dedicated The chart already exposes |
||
| # -- Enable AZ awareness. Adds a topology spread constraint to distribute indexer pods | ||
| # evenly across zones, and enables topology-aware routing on the indexer service so | ||
| # traffic prefers same-zone endpoints. Uses the node-level `topology.kubernetes.io/zone` | ||
| # label. | ||
| enabled: false | ||
|
|
||
| searcher: | ||
| enabled: true | ||
| replicaCount: 3 | ||
|
|
||
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.
When an install already sets a global or indexer
topologySpreadConstraintsentry withtopologyKey: topology.kubernetes.io/zoneandwhenUnsatisfiable: ScheduleAnyway, enablingazAwarenessunconditionally prepends another constraint with the same pair before rendering the user-supplied list. Kubernetes only permits onetopologySpreadConstraintfor eachtopologyKey/whenUnsatisfiablepair, so that common existing zone-spread configuration renders an invalid StatefulSet and blocks the upgrade; skip or merge the generated constraint when the user already supplies one.Useful? React with 👍 / 👎.