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

Schedule Elasticsearch pods on infra nodes created by setting storage parameter in Jaeger custom resource

XMLWordPrintable

    • False
    • None
    • False

      Scheduled the Jaeger elastic search pods to the infra nodes. Other than these pods all the smcp components such as Prometheus, kiali were able to schedule on the infra, but for elastic search, the tolerations don't make any changes and the pods were scheduled on worker instead of infra -
      runtime:
      components:
      jaeger:
      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
         
        -  For Jaeger pod it's not taken the values set on the control plane deployment. 
      • Tested the same configuration for Prometheus or for Kiali and it's working.

              frherrer@redhat.com Francisco Herrera Lira
              rhn-support-ankhande Anjali Khandelwal
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: