[stable/concourse] hard antiaffinity for workers (#5324)

This commit is contained in:
josecv
2018-05-03 13:45:51 -07:00
committed by k8s-ci-robot
parent 24260ad5f8
commit 613d3bbdde
4 changed files with 16 additions and 1 deletions
+1 -1
View File
@@ -1,5 +1,5 @@
name: concourse
version: 1.3.2
version: 1.4.0
appVersion: 3.10.0
description: Concourse is a simple and scalable CI system.
icon: https://avatars1.githubusercontent.com/u/7809479
+1
View File
@@ -129,6 +129,7 @@ The following table lists the configurable parameters of the Concourse chart and
| `worker.fatalErrors` | Newline delimited strings which, when logged, should trigger a restart of the worker | *See [values.yaml](values.yaml)* |
| `worker.updateStrategy` | `OnDelete` or `RollingUpdate` (requires Kubernetes >= 1.7) | `RollingUpdate` |
| `worker.podManagementPolicy` | `OrderedReady` or `Parallel` (requires Kubernetes >= 1.7) | `Parallel` |
| `worker.hardAntiAffinity` | Should the workers be forced (as opposed to preferred) to be on different nodes? | `false` |
| `persistence.enabled` | Enable Concourse persistence using Persistent Volume Claims | `true` |
| `persistence.worker.storageClass` | Concourse Worker Persistent Volume Storage Class | `generic` |
| `persistence.worker.accessMode` | Concourse Worker Persistent Volume Access Mode | `ReadWriteOnce` |
@@ -116,6 +116,14 @@ spec:
{{ toYaml .Values.worker.additionalAffinities | indent 8 }}
{{- end }}
podAntiAffinity:
{{- if .Values.worker.hardAntiAffinity }}
requiredDuringSchedulingIgnoredDuringExecution:
- labelSelector:
matchLabels:
app: {{ template "concourse.worker.fullname" . }}
release: {{ .Release.Name | quote }}
topologyKey: kubernetes.io/hostname
{{- else }}
preferredDuringSchedulingIgnoredDuringExecution:
- weight: 100
podAffinityTerm:
@@ -124,6 +132,7 @@ spec:
matchLabels:
app: {{ template "concourse.worker.fullname" . }}
release: {{ .Release.Name | quote }}
{{- end }}
volumes:
- name: concourse-keys
secret:
+5
View File
@@ -342,6 +342,11 @@ worker:
# values:
# - "true"
## Whether the workers should be forced to run on separate nodes.
## This is accomplished by setting their AntiAffinity with requiredDuringSchedulingIgnoredDuringExecution as opposed to preferred
## Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#inter-pod-affinity-and-anti-affinity-beta-feature
hardAntiAffinity: false
## Tolerations for the worker nodes.
## Ref: https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/
tolerations: []