Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-343

Affinity configuration not working for istiod

XMLWordPrintable

    • 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.

              rhn-support-tkimura Takayoshi Kimura
              rhn-support-tkimura Takayoshi Kimura
              Votes:
              2 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: