Description of problem:

When deploying an application from ACM hub using the GitOps push model to a registered MicroShift cluster, the deployment completes successfully and resources are visible in Argo CD. However, the ACM Application Topology view continues to display the resources as not yet synced.

This results in inconsistent status reporting between Argo CD and ACM, making it difficult to rely on ACM topology for monitoring the actual state of applications deployed to MicroShift clusters.

Version-Release number of selected component (if applicable):
RHACM 2.14 (hub cluster), MicroShift managed cluster

How reproducible:
Always reproducible

Steps to Reproduce:

1. Register a MicroShift cluster as a managed cluster in ACM following the documented steps for non-OpenShift clusters.

1. Deploy an application using the GitOps push model from the ACM hub.

1. Verify that the application deploys successfully on the MicroShift cluster.

1. Check the ACM Application Topology view for the deployed application.

Actual results:

• The application appears as deployed in Argo CD.

• The ACM Application Topology view shows resources as not synced.

Expected results:

• The ACM Application Topology view should accurately display resource status consistent with Argo CD.

Additional info:

• This behavior is specific to MicroShift clusters integrated with ACM using the push model.

• The issue may relate to the managedCluster CR not containing a proper cluster URL, which prevents ACM from resolving application resource status.

• Reference: https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.14/html/gitops/gitops-overview#register-non-ocp