From feb0bfeec69765a862220e2313da6732db16bc75 Mon Sep 17 00:00:00 2001 From: Christian Coffield Date: Fri, 28 Jul 2023 16:10:33 -0400 Subject: [PATCH] Updated doc w.r.t replication init container --- content/docs/replication/deployment/configmap-secrets.md | 6 +++--- content/docs/replication/upgrade.md | 2 ++ content/v1/replication/deployment/configmap-secrets.md | 6 +++--- content/v2/replication/deployment/configmap-secrets.md | 6 +++--- content/v3/replication/deployment/configmap-secrets.md | 6 +++--- 5 files changed, 14 insertions(+), 12 deletions(-) diff --git a/content/docs/replication/deployment/configmap-secrets.md b/content/docs/replication/deployment/configmap-secrets.md index f6194a229d..6390a0f939 100644 --- a/content/docs/replication/deployment/configmap-secrets.md +++ b/content/docs/replication/deployment/configmap-secrets.md @@ -71,12 +71,12 @@ We provide a helper script which can help create KubeConfig files for a normal u * Using a Certificate Signing Request for a user ```shell cd scripts - ./gen-kubeconfig.sh -u -c -k # where "CN user" is the name of the user & key is the private key of the user + ./gen_kubeconfig.sh -u -c -k # where "CN user" is the name of the user & key is the private key of the user ``` * Create kubeconfig file for a Service Account ```shell cd scripts - ./gen-kubeconfig.sh -s -n + ./gen_kubeconfig.sh -s -n ``` Once you have created the KubeConfig file, you can use it to create the secret. @@ -112,7 +112,7 @@ already has all the required RBAC privileges. Use the following command to first create a KubeConfig file using the helper script in _Cluster B_: ```shell -./gen-kubeconfig.sh -s dell-replication-controller-sa -n dell-replication-controller +./gen_kubeconfig.sh -s dell-replication-controller-sa -n dell-replication-controller ``` Once the KubeConfig file has been generated successfully, use the following command in _Cluster A_ to to create the secret: ```shell diff --git a/content/docs/replication/upgrade.md b/content/docs/replication/upgrade.md index 2902aabe6e..e6588b3057 100644 --- a/content/docs/replication/upgrade.md +++ b/content/docs/replication/upgrade.md @@ -94,3 +94,5 @@ This option will only work if you have previously installed replication via Helm CRD `dellcsireplicationgroups.replication.storage.dell.com` has been updated to version `v1` in CSM Replication v1.4.0. To facilitate the continued use of existing `DellCSIReplicationGroup` CR objects after upgrading to CSM Replication v1.4.0 or later, an `init container` will be deployed during upgrade. The `init container` updates the existing CRs with necessary steps for their continued use. > _**Note**_: Do not update the CRD as part of upgrade. An `init container` included in the replication controller pod takes care of updating existing CRD and CR versions. + +Starting from CSM Replication v1.5.1, the `init container` has been removed. Therefore, when upgrading from versions older than v1.4.0 to v1.5.1 or any later versions, it is mandatory to perform an intermediate upgrade to either v1.4.0 or v1.5.0 before proceeding with any further upgrades. diff --git a/content/v1/replication/deployment/configmap-secrets.md b/content/v1/replication/deployment/configmap-secrets.md index 9bebc22f87..018cf18246 100644 --- a/content/v1/replication/deployment/configmap-secrets.md +++ b/content/v1/replication/deployment/configmap-secrets.md @@ -71,12 +71,12 @@ We provide a helper script which can help create KubeConfig files for a normal u * Using a Certificate Signing Request for a user ```shell cd scripts - ./gen-kubeconfig.sh -u -c -k # where "CN user" is the name of the user & key is the private key of the user + ./gen_kubeconfig.sh -u -c -k # where "CN user" is the name of the user & key is the private key of the user ``` * Create kubeconfig file for a Service Account ```shell cd scripts - ./gen-kubeconfig.sh -s -n + ./gen_kubeconfig.sh -s -n ``` Once you have created the KubeConfig file, you can use it to create the secret. @@ -109,7 +109,7 @@ already has all the required RBAC privileges. ##### Example Use the following command to first create a KubeConfig file using the helper script in _Cluster B_: ```shell -./gen-kubeconfig.sh -s dell-replication-controller-sa -n dell-replication-controller +./gen_kubeconfig.sh -s dell-replication-controller-sa -n dell-replication-controller ``` Once the KubeConfig file has been generated successfully, use the following command in _Cluster A_ to to create the secret: ```shell diff --git a/content/v2/replication/deployment/configmap-secrets.md b/content/v2/replication/deployment/configmap-secrets.md index b93d82e71b..b78aa68e82 100644 --- a/content/v2/replication/deployment/configmap-secrets.md +++ b/content/v2/replication/deployment/configmap-secrets.md @@ -71,12 +71,12 @@ We provide a helper script which can help create KubeConfig files for a normal u * Using a Certificate Signing Request for a user ```shell cd scripts - ./gen-kubeconfig.sh -u -c -k # where "CN user" is the name of the user & key is the private key of the user + ./gen_kubeconfig.sh -u -c -k # where "CN user" is the name of the user & key is the private key of the user ``` * Create kubeconfig file for a Service Account ```shell cd scripts - ./gen-kubeconfig.sh -s -n + ./gen_kubeconfig.sh -s -n ``` Once you have created the KubeConfig file, you can use it to create the secret. @@ -109,7 +109,7 @@ already has all the required RBAC privileges. ##### Example Use the following command to first create a KubeConfig file using the helper script in _Cluster B_ - ```shell -./gen-kubeconfig.sh -s dell-replication-controller-sa -n dell-replication-controller +./gen_kubeconfig.sh -s dell-replication-controller-sa -n dell-replication-controller ``` Once the KubeConfig file has been generated successfully, use the following command in _Cluster A_ to to create the secret: ```shell diff --git a/content/v3/replication/deployment/configmap-secrets.md b/content/v3/replication/deployment/configmap-secrets.md index 677a309e7a..cb37533148 100644 --- a/content/v3/replication/deployment/configmap-secrets.md +++ b/content/v3/replication/deployment/configmap-secrets.md @@ -71,12 +71,12 @@ We provide a helper script which can help create KubeConfig files for a normal u * Using a Certificate Signing Request for a user ```shell cd scripts - ./gen-kubeconfig.sh -u -c -k # where "CN user" is the name of the user & key is the private key of the user + ./gen_kubeconfig.sh -u -c -k # where "CN user" is the name of the user & key is the private key of the user ``` * Create kubeconfig file for a Service Account ```shell cd scripts - ./gen-kubeconfig.sh -s -n + ./gen_kubeconfig.sh -s -n ``` Once you have created the KubeConfig file, you can use it to create the secret. @@ -109,7 +109,7 @@ already has all the required RBAC privileges. ##### Example Use the following command to first create a KubeConfig file using the helper script in _Cluster B_ - ```shell -./gen-kubeconfig.sh -s default -n dell-replication-controller +./gen_kubeconfig.sh -s default -n dell-replication-controller ``` Once the KubeConfig file has been generated successfully, use the following command in _Cluster A_ to to create the secret: ```shell