-
Bug
-
Resolution: Won't Do
-
Normal
-
ACM 2.10.0, ACM 2.9.0, ACM 2.11.0
-
False
-
None
-
False
-
-
-
None
- Published doc: https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.10/html/add-ons/add-ons-overview#add-ons-klusterlet
- Source: https://github.com/stolostron/rhacm-docs/tree/2.11_stage/add-ons
We need to add 1.4 disabling cluster-proxy-addon - the documentation should just state that if you do not need a reverse proxy to have your clusters reach RHACM you can disable the cluster-proxy-addon through not the klusterletAddonConfig but the multiclusterhub-config - the `cluster-proxy-addon` deployments will stop if the component of the same name is disabled in MCE. Examples :
apiVersion: operator.open-cluster-management.io/v1 kind: MultiClusterEngine metadata: name: multiclusterengine spec: overrides: components: - name: cluster-proxy-addon enabled: false
or
oc patch MultiClusterEngine <multiclusterengine-name> --type=json -p='[{"op": "add", "path": "/spec/overrides/components/-","value":{"name":"cluster-proxy-addon","enabled":false}}]'
can be used for that purpose.
and you can link to https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.10/html-single/clusters/index#deployed-components which does state how to enable - could instead of the examples state to change the component cluster-proxy-addon to enabled: false from the default enabled: true.