Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-4750 Doc: How to configure OADP NodeAgents on nodes with worker, infra or custom labels
  3. OADP-4752

(QE) Verify for ( Doc: How to configure OADP NodeAgents on nodes with worker, infra or custom labels )

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • OADP 1.4.1
    • None
    • QE-Task
    • None
    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • ToDo
    • 0
    • 0.000
    • Very Likely
    • 0
    • None
    • Unset
    • Unknown

      Description of problem:

      OADP's DPA use the k8s nodeSelector to pick which nodes can run the nodeAgent.

      Any label specified must match the labels on EACH node.

       

      The below example is an anti-pattern and will not work unless both labels are on the node.

       

       28   configuration:
       29     nodeAgent:
       30       enable: true
       31       podConfig:
       32         nodeSelector:
       33           'node-role.kubernetes.io/infra: ""'
       34           'node-role.kubernetes.io/worker: ""'

       

       

      A better solution would be to label any node w/ 'node-role.kubernetes.io/nodeAgent: ""

      where the customer would like to be able to run the nodeAgent

      Then configure the DPA as follows:

       28   configuration:
       29     nodeAgent:
       30       enable: true
       31       podConfig:
       32         nodeSelector:
       33           'node-role.kubernetes.io/nodeAgent: ""'

                 

              rhn-support-prajoshi Prasad Joshi
              talayan@redhat.com Tareq Alayan
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: