Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-7947

ovnkube-master and multus-admission-controller pods do not have the same tolerations as other hypershift CP pods

XMLWordPrintable

    • Important
    • No
    • SDN Sprint 233
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      When running on hypershift, pods managed by the CNO do not get the same tolerations as other pods in the control plane namespace:
      
        - effect: NoSchedule
          key: hypershift.openshift.io/control-plane
          operator: Equal
          value: "true"
        - effect: NoSchedule
          key: hypershift.openshift.io/cluster
          operator: Equal
          value: CLUSTER-NS-NAME
       

      Version-Release number of selected component (if applicable):

       

      How reproducible:

      Always

      Steps to Reproduce:

      1. Create a HyperShift cluster with release 4.12.4
      2. Look at the taints for CNO-managed pods in the hosted control plane namespace.
      

      Actual results:

      Pods do not have `hypershift.openshift.io/control-plane` or `hypershift.openshift.io/cluster` taints.

      Expected results:

      Pods have `hypershift.openshift.io/control-plane` and `hypershift.openshift.io/cluster` taints.

      Additional info:

       

              bpickard@redhat.com Ben Pickard
              cewong@redhat.com Cesar Wong
              Anurag Saxena Anurag Saxena
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: