1. Fix version/s:
ACM 2.13 (and backport to 2.12 docs if possible)

2. Type of documentation change:
☑ We need to update an existing topic

3. Location of update (link to where the documentation update should go):

• Customer Portal published version:
  https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.13/html/install/installing#upgrading-hub

• Doc staged repo:
  https://github.com/stolostron/rhacm-docs

4. GA content requirements:

• Steps / Diff / Known Issue:
  In ACM 2.13, GitOps/ArgoCD switched from long-lived tokens to short-lived tokens for security reasons. This requires the managedserviceaccount component in MCE to be enabled. If this is disabled during upgrade, ArgoCD loses connectivity to managed clusters, resulting in errors and Applications showing as Unknown in ArgoCD.

• Required access level:
  Cluster Administrator

• Verification:
  After upgrade, verify that the managedserviceaccount component is enabled:
   

  oc get mce multiclusterengine -o yaml | grep -A3 managedserviceaccount 

  It should show enabled: true.

5. Bug details (diff/problem/change):

Problem:
The current ACM upgrade documentation (2.12 → 2.13) does not mention the prerequisite of enabling the managedserviceaccount component before upgrade if GitOps/ArgoCD is used. Customers upgrading without enabling this face GitOps failures, including:

• ArgoCD logs show credential errors:
   

  error synchronizing cache state : the server has asked for the client to provide credentials

   

• ArgoCD Applications appear in Unknown state.

• Customers may attempt to regenerate ArgoCD secrets manually, which is unnecessary.

Change requested:
Update the upgrade documentation at:
https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.13/html/install/installing#upgrading-hub

Either:

• Add a note in the Important section stating:

  If you are using GitOps/ArgoCD, ensure that the managedserviceaccount component in MCE is enabled before upgrading ACM from 2.12 to 2.13.

OR

• Add a new prerequisite section under the upgrade docs with this detail.