Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replication doc updates for removing init container usage #729

Merged
merged 1 commit into from
Jul 31, 2023
Merged

Replication doc updates for removing init container usage #729

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions content/docs/replication/deployment/configmap-secrets.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <CN user> -c <CSR> -k <key> # where "CN user" is the name of the user & key is the private key of the user
./gen_kubeconfig.sh -u <CN user> -c <CSR> -k <key> # 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 <sa-name> -n <namespace>
./gen_kubeconfig.sh -s <sa-name> -n <namespace>
```
Once you have created the KubeConfig file, you can use it to create the secret.

Expand Down Expand Up @@ -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
Expand Down
2 changes: 2 additions & 0 deletions content/docs/replication/upgrade.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
6 changes: 3 additions & 3 deletions content/v1/replication/deployment/configmap-secrets.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <CN user> -c <CSR> -k <key> # where "CN user" is the name of the user & key is the private key of the user
./gen_kubeconfig.sh -u <CN user> -c <CSR> -k <key> # 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 <sa-name> -n <namespace>
./gen_kubeconfig.sh -s <sa-name> -n <namespace>
```
Once you have created the KubeConfig file, you can use it to create the secret.

Expand Down Expand Up @@ -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
Expand Down
6 changes: 3 additions & 3 deletions content/v2/replication/deployment/configmap-secrets.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <CN user> -c <CSR> -k <key> # where "CN user" is the name of the user & key is the private key of the user
./gen_kubeconfig.sh -u <CN user> -c <CSR> -k <key> # 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 <sa-name> -n <namespace>
./gen_kubeconfig.sh -s <sa-name> -n <namespace>
```
Once you have created the KubeConfig file, you can use it to create the secret.

Expand Down Expand Up @@ -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
Expand Down
6 changes: 3 additions & 3 deletions content/v3/replication/deployment/configmap-secrets.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <CN user> -c <CSR> -k <key> # where "CN user" is the name of the user & key is the private key of the user
./gen_kubeconfig.sh -u <CN user> -c <CSR> -k <key> # 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 <sa-name> -n <namespace>
./gen_kubeconfig.sh -s <sa-name> -n <namespace>
```
Once you have created the KubeConfig file, you can use it to create the secret.

Expand Down Expand Up @@ -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
Expand Down