Upgrade passmower, set topologySpreadConstraints
This commit is contained in:
@@ -11,7 +11,7 @@ helmCharts:
|
||||
releaseName: *name
|
||||
repo: oci://ghcr.io/passmower/charts
|
||||
valuesFile: values.yaml
|
||||
version: 2.4.0
|
||||
version: 2.4.1
|
||||
|
||||
resources:
|
||||
- ssh://git@git.k-space.ee/secretspace/kube/passmower # secrets: email-credentials, github-client, slack-client
|
||||
|
||||
@@ -108,3 +108,17 @@ nodeSelector: {}
|
||||
tolerations: []
|
||||
|
||||
affinity: {}
|
||||
|
||||
# Spread the replicas one per node. Without this the scheduler packs two onto
|
||||
# whichever worker is emptiest, the descheduler's RemoveDuplicates strategy
|
||||
# calls that a duplicate and evicts one every --descheduling-interval (5m),
|
||||
# and the replacement lands on the same node again - an eviction loop that
|
||||
# shows up as pod churn with zero container restarts.
|
||||
topologySpreadConstraints:
|
||||
- maxSkew: 1
|
||||
topologyKey: kubernetes.io/hostname
|
||||
whenUnsatisfiable: DoNotSchedule
|
||||
labelSelector:
|
||||
matchLabels:
|
||||
app.kubernetes.io/name: passmower
|
||||
app.kubernetes.io/instance: passmower
|
||||
|
||||
Reference in New Issue
Block a user