Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-6016

klusterlet addon nodeselector and tolerations are not propagated on the cluster-proxy-service-proxy deployment

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • ACM 2.8.1
    • ACM 2.8.0
    • Server Foundation
    • None
    • False
    • None
    • False
    • +
    • No

      Description of problem:

       

      klusterlet addon nodeselector and tolerations are not propagated on the cluster-proxy-service-proxy deployment

       

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

      How reproducible: Always

      Steps to Reproduce:

       
      Here are the details for my reproducer.

      1.  

       
      {{apiVersion: addon.open-cluster-management.io/v1alpha1
      kind: AddOnDeploymentConfig
      metadata:
      name: deploy-config
      namespace: open-cluster-management-hub
      spec:
      nodePlacement:
      nodeSelector:
      node-role.kubernetes.io/master: ''
      tolerations:

      • effect: NoSchedule
        key: node-role.kubernetes.io/master
        operator: Exists}}
          #  

       
      {{# oc patch clustermanagementaddons cluster-proxy --type='json' -p='[{"op":"add", "path":"/spec/supportedConfigs", "value":[{"group":"addon.open-cluster-management.io","resource":"addondeploymentconfigs", "defaultConfig":{"name":"deploy-config","namespace":"open-cluster-management-hub"}}]}]'

      clustermanagementaddon.addon.open-cluster-management.io/cluster-proxy patched

      1. oc patch clustermanagementaddons governance-policy-framework --type='json' -p='[{"op":"add", "path":"/spec/supportedConfigs", "value":[{"group":"addon.open-cluster-management.io","resource":"addondeploymentconfigs", "defaultConfig":{"name":"deploy-config","namespace":"open-cluster-management-hub"}}]}]'
        clustermanagementaddon.addon.open-cluster-management.io/governance-policy-framework patched}}
          # From the managed cluster:

       
      {{$ oc get deploy cluster-proxy-service-proxy -o=jsonpath='{ .spec.template.spec.tolerations}' | jq
      [
      {
      "effect": "NoSchedule",
      "key": "dedicated",
      "operator": "Equal",
      "value": "infra"
      },
      {
      "effect": "NoSchedule",
      "key": "node-role.kubernetes.io/infra",
      "operator": "Exists"
      }
      ]

      $ oc get deploy cluster-proxy-proxy-agent -o=jsonpath='

      { .spec.template.spec.tolerations}

      ' | jq
      [

      { "effect": "NoSchedule", "key": "node-role.kubernetes.io/master", "operator": "Exists" }

      ]

      $ oc get deploy governance-policy-framework -o=jsonpath='{ .spec.template.spec.tolerations}' | jq
      [
      {
      "effect": "NoSchedule",
      "key": "node-role.kubernetes.io/master",
      "operator": "Exists"
      }
      ]}}
       
       

      Actual results:

      If you check the above command outputs, you will see that the nodeselector and tolerations are propagated for other deployments, but not cluster-proxy-service-proxy.

      Expected results:

      The configs should be propagated on the managed clusters

      Additional info:

              zxue@redhat.com ZHAO XUE
              rhn-support-mlele Mihir Lele
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: