search

drone / charts

Helm charts for the Drone platform on Kubernetes
Other
166 stars 116 forks source link

Add option to pass in topologySpreadConstraints. #38

Closed fpiesche closed 2 years ago

fpiesche commented 3 years ago

This allows to e.g. ensure there is at least one pod scheduled on a machine for each architecture in a multi-arch cluster (which is my specific use case). I've tested this change to ensure creation of one runner per architecture on my personal cluster using the commented example in values.yml.

fpiesche commented 3 years ago

I've left the required kubeVersion at 1.13 as using topologySpreadConstraints would normally bump this to 1.19 - instead I've opted to take the pattern used in e.g. the nginx chart and wrapped only the topologySpreadConstraints in the Deployment spec in a semverCompare for 1.19.