From d7da80b048f3bfe42858a64c52c27b2a4a98463e Mon Sep 17 00:00:00 2001 From: Mario Manno Date: Wed, 15 Mar 2023 14:44:59 +0100 Subject: [PATCH] Registration reference, summary did not mention ClusterRegistrationToken --- docs/ref-registration.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/ref-registration.md b/docs/ref-registration.md index 3d65d6d2b..1ddfda6b3 100644 --- a/docs/ref-registration.md +++ b/docs/ref-registration.md @@ -4,8 +4,7 @@ Detailed analysis of the registration process for clusters. This shows the inter It's important to note that there are multiple ways to start this: * Creating a bootstrap config. Fleet does this for the local agent. -* Creating a `Cluster` resource with a kubeconfig. Rancher does this for downstream clusters. -* Create a `Cluster` resource with an id. -* Create a `ClusterRegistration` resource. +* Creating a `Cluster` resource with a kubeconfig. Rancher does this for downstream clusters. See [manager-initiated registration](./cluster-registration.md#manager-initiated). +* Create a `ClusterRegistrationToken` resource, optionally create a `Cluster` resource for a pre-defined (`clientID`) cluster. See [agent-initiated registration](./cluster-registration.md#agent-initiated). ![Registration](/img/FleetRegistration.svg)