diff --git a/content/docs/deployment/csmoperator/drivers/powermax.md b/content/docs/deployment/csmoperator/drivers/powermax.md index 9a2ce25372..44c1b6532e 100644 --- a/content/docs/deployment/csmoperator/drivers/powermax.md +++ b/content/docs/deployment/csmoperator/drivers/powermax.md @@ -353,27 +353,27 @@ Create a secret named powermax-certs in the namespace where the CSI PowerMax dri primaryURL: https://primary-1.unisphe.re:8443 # primary unisphere for arrayID backupURL: https://backup-1.unisphe.re:8443 # backup unisphere for arrayID proxyCredentialSecrets: - - proxy-secret-11 # credential secret for primary unisphere, e.g., powermax-creds - - proxy-secret-12 # credential secret for backup unisphere, e.g., powermax-creds + - primary-unisphere-secret-1 # credential secret for primary unisphere, e.g., powermax-creds + - backup-unisphere-secret-1 # credential secret for backup unisphere, e.g., powermax-creds - storageArrayId: "000000000002" primaryURL: https://primary-2.unisphe.re:8443 backupURL: https://backup-2.unisphe.re:8443 proxyCredentialSecrets: - - proxy-secret-21 - - proxy-secret-22 + - primary-unisphere-secret-2 + - backup-unisphere-secret-2 managementServers: - url: https://primary-1.unisphe.re:8443 # primary unisphere endpoint - arrayCredentialSecret: primary-1-secret # primary credential secret e.g., powermax-creds + arrayCredentialSecret: primary-unisphere-secret-1 # primary credential secret e.g., powermax-creds skipCertificateValidation: true - url: https://backup-1.unisphe.re:8443 # backup unisphere endpoint - arrayCredentialSecret: backup-1-secret # backup credential secret e.g., powermax-creds + arrayCredentialSecret: backup-unisphere-secret-1 # backup credential secret e.g., powermax-creds skipCertificateValidation: false # value false, to verify unisphere certificate and provide certSecret certSecret: primary-certs # unisphere verification certificate - url: https://primary-2.unisphe.re:8443 - arrayCredentialSecret: primary-2-secret + arrayCredentialSecret: primary-unisphere-secret-2 skipCertificateValidation: true - url: https://backup-2.unisphe.re:8443 - arrayCredentialSecret: backup-2-secret + arrayCredentialSecret: backup-unisphere-secret-2 skipCertificateValidation: false certSecret: primary-certs ``` diff --git a/content/docs/deployment/helm/drivers/installation/powermax.md b/content/docs/deployment/helm/drivers/installation/powermax.md index 3e49863f1f..a7f6397521 100644 --- a/content/docs/deployment/helm/drivers/installation/powermax.md +++ b/content/docs/deployment/helm/drivers/installation/powermax.md @@ -347,11 +347,11 @@ CRDs should be configured during replication prepare stage with repctl as descri |defaultCredentialsSecret| This secret name refers to:
1 The proxy credentials if the driver is installed with proxy in StandAlone mode.
2. The default Unisphere credentials if credentialsSecret is not specified for a management server. | Yes | powermax-creds | | storageArrays| This section refers to the list of arrays managed by the driver and Reverse Proxy in StandAlone mode. | - | - | | storageArrayId | This refers to PowerMax Symmetrix ID. | Yes | 000000000001| -| endpoint | This refers to the URL of the Unisphere server managing _storageArrayId_. If authorization is enabled, endpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on | Yes if Reverse Proxy mode is _StandAlone_ | https://primary-1.unisphe.re:8443 | -| backupEndpoint | This refers to the URL of the backup Unisphere server managing _storageArrayId_, if Reverse Proxy is installed in _StandAlone_ mode. If authorization is enabled, backupEndpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on | Yes | https://backup-1.unisphe.re:8443 | +| endpoint | This refers to the URL of the Unisphere server managing _storageArrayId_. If authorization is enabled, endpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on | Yes if Reverse Proxy mode is _StandAlone_ | https\://primary-1.unisphe.re:8443 | +| backupEndpoint | This refers to the URL of the backup Unisphere server managing _storageArrayId_, if Reverse Proxy is installed in _StandAlone_ mode. If authorization is enabled, backupEndpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on | Yes | https\://backup-1.unisphe.re:8443 | | managementServers | This section refers to the list of configurations for Unisphere servers managing powermax arrays. | - | - | -| endpoint | This refers to the URL of the Unisphere server. If authorization is enabled, endpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on | Yes | https://primary-1.unisphe.re:8443 | -| credentialsSecret| This refers to the user credentials for _endpoint_ | Yes| primary-1-secret| +| endpoint | This refers to the URL of the Unisphere server. If authorization is enabled, endpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on | Yes | https\://primary-1.unisphe.re:8443 | +| credentialsSecret| This refers to the user credentials for _endpoint_ | Yes| primary-unisphere-secret-1| | skipCertificateValidation | This parameter should be set to false if you want to do client-side TLS verification of Unisphere for PowerMax SSL certificates. | No | "True" | | certSecret | The name of the secret in the same namespace containing the CA certificates of the Unisphere server | Yes, if skipCertificateValidation is set to false | Empty| | limits | This refers to various limits for Reverse Proxy | No | - | @@ -472,7 +472,7 @@ global: backupEndpoint: https://backup-2.unisphe.re:8443 managementServers: - endpoint: https://primary-1.unisphe.re:8443 - credentialsSecret: primary-1-secret + credentialsSecret: primary-unisphere-secret-1 skipCertificateValidation: false certSecret: primary-cert limits: @@ -481,13 +481,13 @@ global: maxOutStandingRead: 50 maxOutStandingWrite: 50 - endpoint: https://backup-1.unisphe.re:8443 - credentialsSecret: backup-1-secret + credentialsSecret: backup-unisphere-secret-1 skipCertificateValidation: true - endpoint: https://primary-2.unisphe.re:8443 - credentialsSecret: primary-2-secret + credentialsSecret: primary-unisphere-secret-2 skipCertificateValidation: true - endpoint: https://backup-2.unisphe.re:8443 - credentialsSecret: backup-2-secret + credentialsSecret: backup-unisphere-secret-2 skipCertificateValidation: true # "csireverseproxy" refers to the subchart csireverseproxy diff --git a/content/v1/deployment/helm/drivers/installation/powermax.md b/content/v1/deployment/helm/drivers/installation/powermax.md index 59e21ba256..8e5b15258d 100644 --- a/content/v1/deployment/helm/drivers/installation/powermax.md +++ b/content/v1/deployment/helm/drivers/installation/powermax.md @@ -293,10 +293,10 @@ CRDs should be configured during replication prepare stage with repctl as descri |defaultCredentialsSecret| This secret name refers to:
1 The proxy credentials if the driver is installed with proxy in StandAlone mode.
2. The default Unisphere credentials if credentialsSecret is not specified for a management server. | Yes | powermax-creds | | storageArrays| This section refers to the list of arrays managed by the driver and Reverse Proxy in StandAlone mode. | - | - | | storageArrayId | This refers to PowerMax Symmetrix ID. | Yes | 000000000001| -| endpoint | This refers to the URL of the Unisphere server managing _storageArrayId_. If authorization is enabled, endpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on | Yes if Reverse Proxy mode is _StandAlone_ | https://primary-1.unisphe.re:8443 | -| backupEndpoint | This refers to the URL of the backup Unisphere server managing _storageArrayId_, if Reverse Proxy is installed in _StandAlone_ mode. If authorization is enabled, backupEndpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on | Yes | https://backup-1.unisphe.re:8443 | +| endpoint | This refers to the URL of the Unisphere server managing _storageArrayId_. If authorization is enabled, endpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on | Yes if Reverse Proxy mode is _StandAlone_ | https\://primary-1.unisphe.re:8443 | +| backupEndpoint | This refers to the URL of the backup Unisphere server managing _storageArrayId_, if Reverse Proxy is installed in _StandAlone_ mode. If authorization is enabled, backupEndpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on | Yes | https\://backup-1.unisphe.re:8443 | | managementServers | This section refers to the list of configurations for Unisphere servers managing powermax arrays. | - | - | -| endpoint | This refers to the URL of the Unisphere server. If authorization is enabled, endpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on | Yes | https://primary-1.unisphe.re:8443 | +| endpoint | This refers to the URL of the Unisphere server. If authorization is enabled, endpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on | Yes | https\://primary-1.unisphe.re:8443 | | credentialsSecret| This refers to the user credentials for _endpoint_ | Yes| primary-1-secret| | skipCertificateValidation | This parameter should be set to false if you want to do client-side TLS verification of Unisphere for PowerMax SSL certificates. | No | "True" | | certSecret | The name of the secret in the same namespace containing the CA certificates of the Unisphere server | Yes, if skipCertificateValidation is set to false | Empty| diff --git a/content/v1/deployment/rpm/modules/installation/authorization/authorization.md b/content/v1/deployment/rpm/modules/installation/authorization/authorization.md index 69d03ef543..b20ee12ed8 100644 --- a/content/v1/deployment/rpm/modules/installation/authorization/authorization.md +++ b/content/v1/deployment/rpm/modules/installation/authorization/authorization.md @@ -35,9 +35,7 @@ yum install -y container-selinux ### Dark Sites -For environments where `yum` will not work, obtain the supported version of container-selinux for your OS version and install it. - -The container-selinux RPMs for CentOS/RedHat 7 and 8 can be downloaded from [https://centos.pkgs.org/7/centos-extras-x86_64/](https://centos.pkgs.org/7/centos-extras-x86_64/) and [https://centos.pkgs.org/8-stream/centos-appstream-x86_64/](https://centos.pkgs.org/8-stream/centos-appstream-x86_64/), respectively. +For environments where the package manager `yum` is not available, ensure that you install a supported version of `container-selinux` package that is suitable for your Linux distribution. ## Deploying the CSM Authorization Proxy Server diff --git a/content/v2/deployment/_index.md b/content/v2/deployment/_index.md index f041f5d58d..28f9f27896 100644 --- a/content/v2/deployment/_index.md +++ b/content/v2/deployment/_index.md @@ -19,7 +19,7 @@ The Container Storage Modules and the required CSI Drivers can each be deployed {{% cardpane %}} - {{< card header="[Dell CSI Drivers Installation via Helm](../csidriver/installation/helm)" + {{< card header="[Dell CSI Drivers Installation via Helm](helm/drivers/installation/)" footer="Installs [PowerStore](helm/drivers/installation/powerstore/) [PowerMax](helm/drivers/installation/powermax/) [PowerScale](helm/drivers/installation/isilon/) [PowerFlex](helm/drivers/installation/powerflex/) [Unity XT](helm/drivers/installation/unity/)">}} Dell CSI Helm installer installs the CSI Driver components using the provided Helm charts. [...More on installation instructions](helm/drivers/installation/) diff --git a/content/v2/deployment/helm/drivers/installation/powermax.md b/content/v2/deployment/helm/drivers/installation/powermax.md index 5ddeb19b50..8d8291e19c 100644 --- a/content/v2/deployment/helm/drivers/installation/powermax.md +++ b/content/v2/deployment/helm/drivers/installation/powermax.md @@ -271,10 +271,10 @@ CRDs should be configured during replication prepare stage with repctl as descri |defaultCredentialsSecret| This secret name refers to:
1 The proxy credentials if the driver is installed with proxy in StandAlone mode.
2. The default Unisphere credentials if credentialsSecret is not specified for a management server.| Yes | powermax-creds | | storageArrays| This section refers to the list of arrays managed by the driver and Reverse Proxy in StandAlone mode.| - | - | | storageArrayId | This refers to PowerMax Symmetrix ID.| Yes | 000000000001| -| endpoint | This refers to the URL of the Unisphere server managing _storageArrayId_. If authorization is enabled, endpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on| Yes if Reverse Proxy mode is _StandAlone_ | https://primary-1.unisphe.re:8443 | -| backupEndpoint | This refers to the URL of the backup Unisphere server managing _storageArrayId_, if Reverse Proxy is installed in _StandAlone_ mode. If authorization is enabled, backupEndpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on| Yes | https://backup-1.unisphe.re:8443 | +| endpoint | This refers to the URL of the Unisphere server managing _storageArrayId_. If authorization is enabled, endpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on| Yes if Reverse Proxy mode is _StandAlone_ | https\://primary-1.unisphe.re:8443 | +| backupEndpoint | This refers to the URL of the backup Unisphere server managing _storageArrayId_, if Reverse Proxy is installed in _StandAlone_ mode. If authorization is enabled, backupEndpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on| Yes | https\://backup-1.unisphe.re:8443 | | managementServers | This section refers to the list of configurations for Unisphere servers managing powermax arrays.| - | - | -| endpoint | This refers to the URL of the Unisphere server. If authorization is enabled, endpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on | Yes | https://primary-1.unisphe.re:8443 | +| endpoint | This refers to the URL of the Unisphere server. If authorization is enabled, endpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on | Yes | https\://primary-1.unisphe.re:8443 | | credentialsSecret| This refers to the user credentials for _endpoint_ | Yes| primary-1-secret| | skipCertificateValidation | This parameter should be set to false if you want to do client-side TLS verification of Unisphere for PowerMax SSL certificates.| No | "True" | | certSecret | The name of the secret in the same namespace containing the CA certificates of the Unisphere server | Yes, if skipCertificateValidation is set to false | Empty| diff --git a/content/v2/deployment/rpm/modules/installation/authorization/authorization.md b/content/v2/deployment/rpm/modules/installation/authorization/authorization.md index 3110692a0b..81b48c54ec 100644 --- a/content/v2/deployment/rpm/modules/installation/authorization/authorization.md +++ b/content/v2/deployment/rpm/modules/installation/authorization/authorization.md @@ -35,9 +35,7 @@ yum install -y container-selinux ### Dark Sites -For environments where `yum` will not work, obtain the supported version of container-selinux for your OS version and install it. - -The container-selinux RPMs for CentOS/RedHat 7 and 8 can be downloaded from [https://centos.pkgs.org/7/centos-extras-x86_64/](https://centos.pkgs.org/7/centos-extras-x86_64/) and [https://centos.pkgs.org/8-stream/centos-appstream-x86_64/](https://centos.pkgs.org/8-stream/centos-appstream-x86_64/), respectively. +For environments where the package manager `yum` is not available, ensure that you install a supported version of `container-selinux` package that is suitable for your Linux distribution. ## Deploying the CSM Authorization Proxy Server diff --git a/content/v3/authorization/deployment/rpm/_index.md b/content/v3/authorization/deployment/rpm/_index.md index 7f96516b3b..7e7e3345b3 100644 --- a/content/v3/authorization/deployment/rpm/_index.md +++ b/content/v3/authorization/deployment/rpm/_index.md @@ -36,9 +36,7 @@ yum install -y container-selinux ### Dark Sites -For environments where `yum` will not work, obtain the supported version of container-selinux for your OS version and install it. - -The container-selinux RPMs for CentOS/RedHat 7 and 8 can be downloaded from [https://centos.pkgs.org/7/centos-extras-x86_64/](https://centos.pkgs.org/7/centos-extras-x86_64/) and [https://centos.pkgs.org/8-stream/centos-appstream-x86_64/](https://centos.pkgs.org/8-stream/centos-appstream-x86_64/), respectively. +For environments where the package manager `yum` is not available, ensure that you install a supported version of `container-selinux` package that is suitable for your Linux distribution. ## Deploying the CSM Authorization Proxy Server diff --git a/content/v3/csidriver/features/powerflex.md b/content/v3/csidriver/features/powerflex.md index 0b2b109c74..6e99ef0662 100644 --- a/content/v3/csidriver/features/powerflex.md +++ b/content/v3/csidriver/features/powerflex.md @@ -930,4 +930,4 @@ If such a node is not available, the pods stay in Pending state. This means pods Without storage capacity tracking, pods get scheduled on a node satisfying the topology constraints. If the required capacity is not available, volume attachment to the pods fails, and pods remain in ContainerCreating state. Storage capacity tracking eliminates unnecessary scheduling of pods when there is insufficient capacity. -The attribute `storageCapacity.enabled` in `values.yaml` can be used to enable/disable the feature during driver installation using helm. This is by default set to true. To configure how often the driver checks for changed capacity set `storageCapacity.pollInterval` attribute. In case of driver installed via operator, this interval can be configured in the sample file provided [here](https://github.com/dell/csm-operator/blob/main/samples/storage_csm_powerflex_v280.yaml) by editing the `--capacity-poll-interval` argument present in the provisioner sidecar. \ No newline at end of file +The attribute `storageCapacity.enabled` in `values.yaml` can be used to enable/disable the feature during driver installation using helm. This is by default set to true. To configure how often the driver checks for changed capacity set `storageCapacity.pollInterval` attribute. In case of driver installed via operator, this interval can be configured in the sample file provided [here](https://github.com/dell/csm-operator/blob/v1.4.4/samples/storage_csm_powerflex_v280.yaml ) by editing the `--capacity-poll-interval` argument present in the provisioner sidecar. \ No newline at end of file diff --git a/content/v3/csidriver/features/powerscale.md b/content/v3/csidriver/features/powerscale.md index 0b21d03420..8b953cbad5 100644 --- a/content/v3/csidriver/features/powerscale.md +++ b/content/v3/csidriver/features/powerscale.md @@ -455,7 +455,7 @@ If such a node is not available, the pods stay in Pending state. This means pods Without storage capacity tracking, pods get scheduled on a node satisfying the topology constraints. If the required capacity is not available, volume attachment to the pods fails, and pods remain in ContainerCreating state. Storage capacity tracking eliminates unnecessary scheduling of pods when there is insufficient capacity. -The attribute `storageCapacity.enabled` in `values.yaml` can be used to enable/disable the feature during driver installation using helm. This is by default set to true. To configure how often driver checks for changed capacity set `storageCapacity.pollInterval` attribute. In case of driver installed via operator, this interval can be configured in the sample file provided [here.](https://github.com/dell/csm-operator/blob/main/samples/storage_csm_powerscale_v280.yaml) by editing the `--capacity-poll-interval` argument present in the provisioner sidecar. +The attribute `storageCapacity.enabled` in `values.yaml` can be used to enable/disable the feature during driver installation using helm. This is by default set to true. To configure how often driver checks for changed capacity set `storageCapacity.pollInterval` attribute. In case of driver installed via operator, this interval can be configured in the sample file provided [here.](https://github.com/dell/csm-operator/blob/v1.4.4/samples/storage_csm_powerscale_v280.yaml) by editing the `--capacity-poll-interval` argument present in the provisioner sidecar. ## Node selector in helm template diff --git a/content/v3/csidriver/features/unity.md b/content/v3/csidriver/features/unity.md index 7542e65d9d..6a68b93536 100644 --- a/content/v3/csidriver/features/unity.md +++ b/content/v3/csidriver/features/unity.md @@ -498,7 +498,7 @@ If such a node is not available, the pods stay in Pending state. This means pods Without storage capacity tracking, pods get scheduled on a node satisfying the topology constraints. If the required capacity is not available, volume attachment to the pods fails, and pods remain in ContainerCreating state. Storage capacity tracking eliminates unnecessary scheduling of pods when there is insufficient capacity. Moreover, storage capacity tracking returns `MaximumVolumeSize` parameter, which may be used as an input to the volume creation. -The attribute `storageCapacity.enabled` in `values.yaml` can be used to enable/disable the feature during driver installation using helm. This is by default set to true. To configure how often driver checks for changed capacity set `storageCapacity.pollInterval` attribute. In case of driver installed via operator, this interval can be configured in the sample file provided [here.](https://github.com/dell/csm-operator/blob/main/samples/storage_csm_unity_v280.yaml) by editing the `--capacity-poll-interval` argument present in the provisioner sidecar. +The attribute `storageCapacity.enabled` in `values.yaml` can be used to enable/disable the feature during driver installation using helm. This is by default set to true. To configure how often driver checks for changed capacity set `storageCapacity.pollInterval` attribute. In case of driver installed via operator, this interval can be configured in the sample file provided [here.](https://github.com/dell/csm-operator/blob/v1.4.4/samples/storage_csm_unity_v280.yaml ) by editing the `--capacity-poll-interval` argument present in the provisioner sidecar. ## Dynamic Logging Configuration diff --git a/content/v3/csidriver/installation/helm/powermax.md b/content/v3/csidriver/installation/helm/powermax.md index 1547f01b32..09df896551 100644 --- a/content/v3/csidriver/installation/helm/powermax.md +++ b/content/v3/csidriver/installation/helm/powermax.md @@ -267,10 +267,10 @@ CRDs should be configured during replication prepare stage with repctl as descri |defaultCredentialsSecret| This secret name refers to:
1 The proxy credentials if the driver is installed with proxy in StandAlone mode.
2. The default Unisphere credentials if credentialsSecret is not specified for a management server.| Yes | powermax-creds | | storageArrays| This section refers to the list of arrays managed by the driver and Reverse Proxy in StandAlone mode.| - | - | | storageArrayId | This refers to PowerMax Symmetrix ID.| Yes | 000000000001| -| endpoint | This refers to the URL of the Unisphere server managing _storageArrayId_. If authorization is enabled, endpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on| Yes if Reverse Proxy mode is _StandAlone_ | https://primary-1.unisphe.re:8443 | -| backupEndpoint | This refers to the URL of the backup Unisphere server managing _storageArrayId_, if Reverse Proxy is installed in _StandAlone_ mode. If authorization is enabled, backupEndpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on| Yes | https://backup-1.unisphe.re:8443 | +| endpoint | This refers to the URL of the Unisphere server managing _storageArrayId_. If authorization is enabled, endpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on| Yes if Reverse Proxy mode is _StandAlone_ | https\://primary-1.unisphe.re:8443 | +| backupEndpoint | This refers to the URL of the backup Unisphere server managing _storageArrayId_, if Reverse Proxy is installed in _StandAlone_ mode. If authorization is enabled, backupEndpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on| Yes | https\://backup-1.unisphe.re:8443 | | managementServers | This section refers to the list of configurations for Unisphere servers managing powermax arrays.| - | - | -| endpoint | This refers to the URL of the Unisphere server. If authorization is enabled, endpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on | Yes | https://primary-1.unisphe.re:8443 | +| endpoint | This refers to the URL of the Unisphere server. If authorization is enabled, endpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on | Yes | https\://primary-1.unisphe.re:8443 | | credentialsSecret| This refers to the user credentials for _endpoint_ | Yes| primary-1-secret| | skipCertificateValidation | This parameter should be set to false if you want to do client-side TLS verification of Unisphere for PowerMax SSL certificates.| No | "True" | | certSecret | The name of the secret in the same namespace containing the CA certificates of the Unisphere server | Yes, if skipCertificateValidation is set to false | Empty| diff --git a/content/v3/csidriver/installation/operator/operator_migration.md b/content/v3/csidriver/installation/operator/operator_migration.md index 18d3eba7b2..a056417347 100644 --- a/content/v3/csidriver/installation/operator/operator_migration.md +++ b/content/v3/csidriver/installation/operator/operator_migration.md @@ -56,7 +56,7 @@ description: > - Select *Create instance* under the provided Container Storage Module API - Use the CR backup from step 1 to manually map desired settings to the new CSI driver - As the yaml content may differ, ensure the values held in the step 1 CR backup are present in the new CR before installing the new driver - - Ex: spec.driver.fsGroupPolicy in [PowerMax 2.7 for CSI Operator](https://github.com/dell/dell-csi-operator/blob/main/samples/powermax_v270_k8s_127.yaml#L17C5-L17C18) maps to spec.driver.csiDriverSpec.fSGroupPolicy in [PowerMax 2.10 for CSM Operator](https://github.com/dell/csm-operator/blob/main/samples/storage_csm_powermax_v2100.yaml#L28C7-L28C20) + - Ex: spec.driver.fsGroupPolicy in [PowerMax 2.7 for CSI Operator](https://github.com/dell/dell-csi-operator/blob/main/samples/powermax_v270_k8s_127.yaml#L17C5-L17C18) maps to spec.driver.csiDriverSpec.fSGroupPolicy in [PowerMax 2.9 for CSM Operator](https://github.com/dell/csm-operator/blob/v1.4.4/samples/storage_csm_powermax_v290.yaml#L28 ) >NOTE: Uninstallation of the driver and the Operator is non-disruptive for mounted volumes. Nonetheless you can not create new volume, snapshot or move a Pod. ## Testing diff --git a/content/v3/deployment/csmoperator/drivers/powerflex.md b/content/v3/deployment/csmoperator/drivers/powerflex.md index 4166851386..52ce9487f6 100644 --- a/content/v3/deployment/csmoperator/drivers/powerflex.md +++ b/content/v3/deployment/csmoperator/drivers/powerflex.md @@ -31,7 +31,7 @@ kubectl get csm --all-namespaces - Optionally, enable sdc monitor by setting the enable flag for the sdc-monitor to true. Please note: - **If using sidecar**, you will need to edit the value fields under the HOST_PID and MDM fields by filling the empty quotes with host PID and the MDM IPs. - **If not using sidecar**, leave the enabled field set to false. -##### Example CR: [samples/storage_csm_powerflex_v290.yaml](https://github.com/dell/csm-operator/blob/main/samples/storage_csm_powerflex_v290.yaml) +##### Example CR: [samples/storage_csm_powerflex_v290.yaml](https://github.com/dell/csm-operator/blob/v1.4.4/samples/storage_csm_powerflex_v290.yaml) ```yaml sideCars: # sdc-monitor is disabled by default, due to high CPU usage diff --git a/content/v3/deployment/csmoperator/modules/authorization.md b/content/v3/deployment/csmoperator/modules/authorization.md index 5ed403deb4..1282e8a9fb 100644 --- a/content/v3/deployment/csmoperator/modules/authorization.md +++ b/content/v3/deployment/csmoperator/modules/authorization.md @@ -152,7 +152,7 @@ kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/relea 1. Follow all the [prerequisites](#prerequisite). -2. Create a CR (Custom Resource) for Authorization using the sample file provided [here](https://github.com/dell/csm-operator/blob/main/samples/authorization/csm_authorization_proxy_server_v1100.yaml). This file can be modified to use custom parameters if needed. +2. Create a CR (Custom Resource) for Authorization using the sample file provided [here](https://github.com/dell/csm-operator/blob/v1.4.4/samples/authorization/csm_authorization_proxy_server_v190.yaml ). This file can be modified to use custom parameters if needed. 3. Users should configure the parameters in the CR. This table lists the primary configurable parameters of the Authorization Proxy Server and their default values: @@ -196,7 +196,7 @@ To enable reporting of trace data with [Zipkin](https://zipkin.io/), use the `cs kubectl create secret tls karavi-auth-tls -n authorization --key --cert ``` - If using a self-signed certificate, prepare `samples/authorization/certificate_v190.yaml` provided [here](https://github.com/dell/csm-operator/blob/main/samples/authorization/certificate_v1100.yaml). An entry for each hostname specified in the CR must be added under `dnsNames` for the certificate to be valid for each Ingress. + If using a self-signed certificate, prepare `samples/authorization/certificate_v190.yaml` provided [here](https://github.com/dell/csm-operator/blob/v1.4.4/samples/authorization/certificate_v190.yaml). An entry for each hostname specified in the CR must be added under `dnsNames` for the certificate to be valid for each Ingress. Use this command to create the `karavi-auth-tls` secret: