-
Bug
-
Resolution: Done
-
Normal
-
ACM 2.8.0
-
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.
{{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
- 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
[
]
$ 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