In v1.8 YAMLs we have introduced this anti-affinity for cilium pods:
|
affinity: |
|
podAntiAffinity: |
|
requiredDuringSchedulingIgnoredDuringExecution: |
|
- labelSelector: |
|
matchExpressions: |
|
- key: k8s-app |
|
operator: In |
|
values: |
|
- cilium |
|
topologyKey: "kubernetes.io/hostname" |
However this applies globally, ie also to the cilium-etcd-operator pods:
|
{{- if .Values.global.affinity }} |
|
affinity: |
|
{{ toYaml .Values.global.affinity | indent 8 }} |
|
{{- end }} |
This latter piece was introduced to help scheduling cilium-etcd-operator on the same nodes as Cilium in PR #9901.
I don't think this is intended; while attempting to deploy managed etcd cilium for clustermesh testing, I had to manually edit the cilium-etcd-operator deployment to drop this affinity constraint.
In v1.8 YAMLs we have introduced this anti-affinity for cilium pods:
cilium/install/kubernetes/cilium/values.yaml
Lines 574 to 583 in df97ca1
However this applies globally, ie also to the cilium-etcd-operator pods:
cilium/install/kubernetes/cilium/charts/managed-etcd/templates/cilium-etcd-operator-deployment.yaml
Lines 26 to 29 in df97ca1
This latter piece was introduced to help scheduling cilium-etcd-operator on the same nodes as Cilium in PR #9901.
I don't think this is intended; while attempting to deploy managed etcd cilium for clustermesh testing, I had to manually edit the cilium-etcd-operator deployment to drop this affinity constraint.