cloudnative-pg / cloudnative-pg/charts
Add topology spread constraints
- Dominant language
- Go Template
- Stars
- 621
- Forks
- 265
- Avg merge
- 7d 12h
- Merged PRs (30d)
- 7
Description
Topology spread constraints are necessary for HA environments and should be added to the chart, eg.:
```
topologySpreadConstraints:
- labelSelector:
matchLabels:
cnpg.io/cluster: {{ include "cluster.fullname" . }}
maxSkew: 1
topologyKey: faultdomain
whenUnsatisfiable: ScheduleAnyway
```
Contributor guide
Research direction
Start by locating the chart values and workload template where scheduling options are defined, then compare existing chart conventions. Render the chart with topology spread constraints enabled and verify the generated manifest contains the requested selector, maxSkew, topologyKey, and whenUnsatisfiable settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100