Details
-
Bug
-
Resolution: Done
-
Minor
-
4.12
-
No
-
1
-
T&PS 2024 #2, T&PS 2024 #3
-
2
-
False
-
-
2024-03-19: Out for SME review
Description
Description of problem:
The procedure for installing ArgoCD on the hub cluster is missing the step for applying the disable-cluster-proxy-addon.json patch. This procedure is documented as step 3 in the 4.13 docs but did not make it back into the 4.12 docs:
https://docs.openshift.com/container-platform/4.13/scalability_and_performance/ztp_far_edge/ztp-preparing-the-hub-cluster.html#ztp-configuring-hub-cluster-with-argocd_ztp-preparing-the-hub-cluster
Version-Release number of selected component (if applicable):
{code:none}
4.12
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Step 3 is added with this content: In RHACM 2.7 and later, the multicluster engine enables the cluster-proxy-addon feature by default. To disable this feature, apply the following patch to disable and remove the relevant hub cluster and managed cluster pods that are responsible for this add-on.$ oc patch multiclusterengines.multicluster.openshift.io multiclusterengine --type=merge --patch-file out/argocd/deployment/disable-cluster-proxy-addon.json
Additional info:
Version-Release number of selected component (if applicable):
{code:none}
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
