-
Bug
-
Resolution: Done
-
Major
-
None
-
False
-
False
-
+
-
Undefined
-
-
Sprint 2, Sprint 3
In OSSM 2.0, the istiod configuration supposed to be done via runtime.components.pilot. However, the following affinity configuration doesn't work.
runtime: components: pilot: deployment: replicas: 2 pod: affinity: podAntiAffinity: requiredDuringScheduling: - key: app operator: In topologyKey: kubernetes.io/hostname values: - istiod metadata: labels: foo: bar defaults: pod: tolerations: - effect: NoExecute key: node.kubernetes.io/unreachable operator: Exists tolerationSeconds: 60
In OSSM v1, we can configure affinity on the control plane so it could be a regression.
This is related to OSSMDOC-186. If anything doesn't work via this runtime configuration method, it needs to be documented.
- is blocked by
-
MAISTRA-2057 istio-control helm templates missing _affinity.tpl
- Closed
-
MAISTRA-2223 istio-control helm templates missing _affinity.tpl
- Closed
- relates to
-
MAISTRA-2247 Labels in SMCP not applied to istiod pods
- Closed