Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-6712

Taints and Tolerations - "tolerationSeconds" breaks the deployment

    XMLWordPrintable

Details

    • Bug
    • Resolution: Not a Bug
    • Critical
    • None
    • AMQ 7.10.0.OPR.1.GA
    • None
    • None
    • False
    • None
    • False

    Description

      Tolerations were verified to work by adding toleration (code below) which allowes scheduling of pods on master nodes of OpenShift cluster.

      tolerations:
        - effect: "NoSchedule"
          key: "node-role.kubernetes.io/master"
          operator: "Exists"
          value:
      

      Custom tolerations and node taints can be added. Unfortunately, the tolerationSeconds field is unusable. When this field is added to toleration it breaks both the reconciliation process as well as scheduling of the pods. Stateful set won't scale at all - which is based on my current understanding an OpenShift issue.

      Attachments

        Issue Links

          Activity

            People

              rvais Roman Vais
              rvais Roman Vais
              Roderick Kieley
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: