From f26011426d9804dbc29366b6cd4e6970734805e6 Mon Sep 17 00:00:00 2001 From: welisheva22 Date: Tue, 21 May 2024 12:02:43 -0400 Subject: [PATCH] One more commit - and have the other commits been applied? If not, what to do? (#598) Signed-off-by: welisheva22 Signed-off-by: Etai Lev Ran Co-authored-by: Etai Lev Ran --- website/content/en/docs/main/getting-started/users.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/en/docs/main/getting-started/users.md b/website/content/en/docs/main/getting-started/users.md index c83833a2..a378ec56 100644 --- a/website/content/en/docs/main/getting-started/users.md +++ b/website/content/en/docs/main/getting-started/users.md @@ -62,7 +62,7 @@ To set up ClusterLink on a Kubernetes cluster, follow these steps: This command will deploy the ClusterLink operator on the `clusterlink-operator` namespace and convert the peer certificates to secrets in the namespace where ClusterLink components will be installed. By default, the `clusterlink-system` namespace is used. - in addition it will create a ClusterLink instance custom resource object and deploy it to the operator. + In addition, it will create a ClusterLink instance custom resource object and deploy it to the operator. The operator will then create the ClusterLink components in the `clusterlink-system` namespace and enable ClusterLink in the cluster. The command assumes that `kubectl` is set to the correct peer (K8s cluster) and that the certificates were created by running the previous command on the same working directory.