[release-4.20] [telco-hub] clarify MCE proxy addon configuration

telco-hub/configuration/reference-crs/required/acm/readme.md

@@ -7,13 +7,12 @@
 5. Apply the `acmProvisioning.yaml`.
 6. Create the `acmMirrorRegistryCM.yaml`.
 7. Create the `acmAgentServiceConfig.yaml` (Two PVs are required, so ODF must be configured prior to this step).
-8. The `multicluster-engine` enables the `cluster-proxy-addon` feature by default. Apply the following patch to disable it: `oc patch multiclusterengines.multicluster.openshift.io multiclusterengine --type=merge --patch-file ./disable-cluster-proxy-addon.json`.
-9. Create the `observabilityNS.yaml`.
-10. Create the pull-secret. There are two methods to create the pull-secret:
+8. Create the `observabilityNS.yaml`.
+9. Create the pull-secret. There are two methods to create the pull-secret:
     - The pull-secret multiclusterhub-operator-pull-secret can be automatically created by the ACM policy in pullSecretPolicy.yaml. If secret multiclusterhub-operator-pull-secret exists in open-cluster-management, the policy copy it to ns open-cluster-management-observability. If the previous command returns an empty value, then copy secret pull-secret from ns openshift-config.
     - If you want to use your own pull-secret, you may update the value of .dockerconfigjson in observabilitySecret.yaml.
-11. Create the `observabilityOBC.yaml`.
-12. The Thanos secret will be automatically created by the ACM Policy
+10. Create the `observabilityOBC.yaml`.
+11. The Thanos secret will be automatically created by the ACM Policy
     in `thanosSecretPolicy.yaml`.
     - The `bucket` and the `endpoint` are copied from the ConfigMap
       that the OBC automatically creates in its namespace. The policy
@@ -25,9 +24,9 @@
       `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` are pulled from
       the secret and base64 decoded before being inserted into the
       Thanos secret.
-13. Create the `observabilityMCO.yaml`.
-14. When all the installation is done. Apply the `acmPerfSearch.yaml` .This will configure Search CR called `search-v2-operator` considering different performance and scale optimizations.
-15. When ACM Observability is configured on a managed cluster through the Core or RAN profile, the default ACM Observability configuration must be merged with the RAN monitoring tuning [ReduceMonitoringFootprint.yaml](../../../../../telco-ran/configuration/source-crs/ReduceMonitoringFootprint.yaml) or Core monitoring config [monitoring-config-cm.yaml](../../../../../telco-core/configuration/reference-crs/optional/other/monitoring-config-cm.yaml) respectively. To ensure that these changes persist, ACM has to stop managing the cluster-monitoring-config ConfigMap, which is set in this annotation [here](../../../../../telco-hub/configuration/reference-crs/required/acm/observabilityMCO.yaml#L13).
+12. Create the `observabilityMCO.yaml`.
+13. When all the installation is done. Apply the `acmPerfSearch.yaml` .This will configure Search CR called `search-v2-operator` considering different performance and scale optimizations.
+14. When ACM Observability is configured on a managed cluster through the Core or RAN profile, the default ACM Observability configuration must be merged with the RAN monitoring tuning [ReduceMonitoringFootprint.yaml](../../../../../telco-ran/configuration/source-crs/ReduceMonitoringFootprint.yaml) or Core monitoring config [monitoring-config-cm.yaml](../../../../../telco-core/configuration/reference-crs/optional/other/monitoring-config-cm.yaml) respectively. To ensure that these changes persist, ACM has to stop managing the cluster-monitoring-config ConfigMap, which is set in this annotation [here](../../../../../telco-hub/configuration/reference-crs/required/acm/observabilityMCO.yaml#L13).
 
 Back to [Hub Cluster Setup](../../../../README.md).