You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* allow precreating ACM resources
* Update docs/ACMRegistration.md
Co-authored-by: Ian Miller <34246471+imiller0@users.noreply.github.com>
---------
Co-authored-by: Ian Miller <34246471+imiller0@users.noreply.github.com>
Now your target cluster has a Secret than will allow it to authenticate to the ACM cluster and register itself. Once the registration succeeds, the secret is deleted from the target cluster.
62
+
63
+
## Pre-creating the ManagedCluster and (optionally) KlusterletAddonConfig
64
+
For use cases where flexible and ongoing control over the `ManagedCluster` and (optionally) the `klusterletAddonConfig` CRs is required you may pre-create these artifacts on the ACM hub cluster prior to relocation. This allows the user to control the lifetime and content (eg custom labels on the ManagedCluster) CRs beyond the initial installation phase.
65
+
66
+
When these CRs are pre-created for a cluster you can omit the `managedClusterSet` and `klusterletAddonConfig` fields from the relocation CR. In this case, the Service Account that you create only needs permissions to "get" Secrets for the cluster namespace created by the ManagedCluster.
67
+
68
+
For example (run these commands on your ACM cluster):
69
+
```
70
+
oc create sa -n multicluster-engine acm-registration-sa
0 commit comments