Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-3995

nodeSelector in DPA applies extra "node-role.kubernetes.io/app" label to pod

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • ToDo
    • No
    • Important
    • 8
    • 0
    • Very Likely
    • 0
    • None
    • Unset
    • Unknown

      Description of problem:

      Setting up nodeSelector in restic section in the DPA applies extra "node-role.kubernetes.io/app" label to pod.

      This causes some node-agent pods to not be scheduled as desired,as the pods have:

      spec:
        nodeSelector:
          kubernetes.io/os: linux
          node-role.kubernetes.io/app:  

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

      OADP 1.3

      How reproducible:

      Always

      Steps to Reproduce:
      1. Configure DPA with nodeSeletor in restic section
      2. Pods start with extra label in nodeSelector
      3. 

      Actual results:

      Pods not running in all the desired nodes( Infra nodes)

      Expected results:

      Pods running with only the nodeSelector label

       

      Additional info:

            wnstb Wes Hayutin
            rhn-support-mblach Miguel Blach
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: