Description of problem (possible bug):

• When ACM 2.15.x is installed, the ClusterManagementAddOn for governance-policy-framework is created with spec.installStrategy.type=Manual. After importing a new managed cluster, ACM does not automatically create the corresponding ManagedClusterAddOn.
• Without the managed add-on, the hub never delivers the governance policy framework CRDs to the spoke. Downstream features (for example, labeling the spoke with cluster.open-cluster-management.io/cnv=true so CNV deploys) do not activate because their dependency on the policy framework never materializes.

Version-Release number of selected component (if applicable): acm 2.15-119

How reproducible: Always

Steps to Reproduce:

1. Login to hub
2. oc get clustermanagementaddon governance-policy-framework -o yaml | grep installStrategy → type: Manual.
3. kubectl get managedclusteraddon -n <spoke-namespace> → no governance-policy-framework entry for newly imported clusters.

...

Actual results:

Expected results:

Additional info:

Creating the managed add-on manually (oc apply -f governance-policy-framework.yaml in the spoke namespace) immediately deploys the missing CRDs and unblocks CNV enablement.