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

Default tolerations in SMCP not passed to Jaeger

XMLWordPrintable

    • Sprint 62

      If you add the following snippet to the SMCP, the nodeSelector is passed to the Jaeger resource, but the tolerations are not.

      spec:
        runtime:
          defaults:
            pod:
              nodeSelector:
                node-role.kubernetes.io/infra: ""
              tolerations:
              - effect: NoSchedule
                key: node-role.kubernetes.io/infra
                value: reserved
              - effect: NoExecute
                key: node-role.kubernetes.io/infra
                value: reserved
      

      This results in the Jaeger pod being stuck in Pending state:

      $ oc describe pod jaeger-xyz
      Warning  FailedScheduling  42s    default-scheduler  0/6 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/infra: reserved}, 3 node(s) had untolerated taint {node-role.kubernetes.io/master: }, 5 node(s) didn't match Pod's node affinity/selector. preemption: 0/6 nodes are available: 6 Preemption is not helpful for scheduling.
      

            mluksa@redhat.com Marko Luksa
            mluksa@redhat.com Marko Luksa
            Francisco Herrera Lira
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: