diff --git a/config.toml b/config.toml index 442433bd6c..60fb2b1fb1 100644 --- a/config.toml +++ b/config.toml @@ -172,7 +172,7 @@ enable = false # icon = "fa fa-envelope" # desc = "Discuss development issues around the project" [[params.versions]] - version = "Current(v1.9.0)" + version = "Current(v1.9.1)" url = "https://dell.github.io/csm-docs/docs/" [[params.versions]] diff --git a/content/docs/authorization/release/_index.md b/content/docs/authorization/release/_index.md index 05065d9d40..3bcadd9408 100644 --- a/content/docs/authorization/release/_index.md +++ b/content/docs/authorization/release/_index.md @@ -6,7 +6,7 @@ Description: > Dell Container Storage Modules (CSM) release notes for authorization --- -## Release Notes - CSM Authorization 1.8.0 +## Release Notes - CSM Authorization 1.9.1 diff --git a/content/docs/csidriver/_index.md b/content/docs/csidriver/_index.md index 39f09b5aae..f492451119 100644 --- a/content/docs/csidriver/_index.md +++ b/content/docs/csidriver/_index.md @@ -36,7 +36,7 @@ The CSI Drivers by Dell implement an interface between [CSI](https://kubernetes- {{}} | Features | PowerMax | PowerFlex | Unity XT | PowerScale | PowerStore | |--------------------------|:--------:|:---------:|:---------:|:----------:|:----------:| -| CSI Driver version | 2.9.0 | 2.9.0 | 2.9.0 | 2.9.0 | 2.9.0 | +| CSI Driver version | 2.9.1 | 2.9.1 | 2.9.1 | 2.9.1 | 2.9.1 | | Static Provisioning | yes | yes | yes | yes | yes | | Dynamic Provisioning | yes | yes | yes | yes | yes | | Expand Persistent Volume | yes | yes | yes | yes | yes | diff --git a/content/docs/csidriver/features/powermax.md b/content/docs/csidriver/features/powermax.md index 3a3f6d379f..a9e1a0b65b 100644 --- a/content/docs/csidriver/features/powermax.md +++ b/content/docs/csidriver/features/powermax.md @@ -311,7 +311,8 @@ For example, if `nodeNameTemplate` is _abc-%foo%-hostname_ and nodename is _work ## Controller HA -Starting with version 1.5, the CSI PowerMax driver supports running multiple replicas of the controller Pod. At any time, only one controller Pod is active(leader), and the rest are on standby. In case of a failure, one of the standby Pods becomes active and takes the position of leader. This is achieved by using native leader election mechanisms utilizing `kubernetes leases`. Additionally by leveraging `pod anti-affinity`, no two-controller Pods are ever scheduled on the same node. +Starting with version 1.5, the CSI PowerMax driver supports running multiple replicas of the controller Pod. +Leader election is only applicable for all sidecar containers and driver container will be running in all controller pods . In case of a failure, one of the standby Pods becomes active and takes the position of leader. This is achieved by using native leader election mechanisms utilizing `kubernetes leases`. Additionally by leveraging `pod anti-affinity`, no two-controller Pods are ever scheduled on the same node. To increase or decrease the number of controller Pods, edit the following value in `values.yaml` file: ```yaml diff --git a/content/docs/csidriver/features/powerscale.md b/content/docs/csidriver/features/powerscale.md index d6d942c16b..23b02971a8 100644 --- a/content/docs/csidriver/features/powerscale.md +++ b/content/docs/csidriver/features/powerscale.md @@ -289,8 +289,7 @@ spec: ## Controller HA -CSI PowerScale driver version 1.4.0 and later supports running multiple replicas of the controller pod. At any time, only one controller pod is active(leader), and the rest are on standby. -In case of a failure, one of the standby pods becomes active and takes the position of leader. This is achieved by using native leader election mechanisms utilizing `kubernetes leases`. +CSI PowerScale driver version 1.4.0 and later supports running multiple replicas of the controller pod. Leader election is only applicable for all sidecar containers and driver container will be running in all controller pods. In case of a failure, one of the standby pods becomes active and takes the position of leader. This is achieved by using native leader election mechanisms utilizing `kubernetes leases`. Additionally by leveraging `pod anti-affinity`, no two-controller pods are ever scheduled on the same node. diff --git a/content/docs/csidriver/installation/helm/isilon.md b/content/docs/csidriver/installation/helm/isilon.md index 5b5f2d07a2..31f3a4c38b 100644 --- a/content/docs/csidriver/installation/helm/isilon.md +++ b/content/docs/csidriver/installation/helm/isilon.md @@ -94,13 +94,13 @@ CRDs should be configured during replication prepare stage with repctl as descri **Steps** -1. Run `git clone -b v2.9.0 https://github.com/dell/csi-powerscale.git` to clone the git repository. +1. Run `git clone -b v2.9.1 https://github.com/dell/csi-powerscale.git` to clone the git repository. 2. Ensure that you have created the namespace where you want to install the driver. You can run `kubectl create namespace isilon` to create a new one. The use of "isilon" as the namespace is just an example. You can choose any name for the namespace. 3. Collect information from the PowerScale Systems like IP address, IsiPath, username, and password. Make a note of the value for these parameters as they must be entered in the *secret.yaml*. -4. Download `wget -O my-isilon-settings.yaml https://raw.githubusercontent.com/dell/helm-charts/csi-isilon-2.9.0/charts/csi-isilon/values.yaml` into `cd ../dell-csi-helm-installer` to customize settings for installation. +4. Download `wget -O my-isilon-settings.yaml https://raw.githubusercontent.com/dell/helm-charts/csi-isilon-2.9.1/charts/csi-isilon/values.yaml` into `cd ../dell-csi-helm-installer` to customize settings for installation. 5. Edit *my-isilon-settings.yaml* to set the following parameters for your installation: The following table lists the primary configurable parameters of the PowerScale driver Helm chart and their default values. More detailed information can be - found in the [`values.yaml`](https://github.com/dell/helm-charts/blob/csi-isilon-2.9.0/charts/csi-isilon/values.yaml) file in this repository. + found in the [`values.yaml`](https://github.com/dell/helm-charts/blob/csi-isilon-2.9.1/charts/csi-isilon/values.yaml) file in this repository. | Parameter | Description | Required | Default | | --------- | ----------- | -------- |-------- | @@ -210,7 +210,7 @@ Create isilon-creds secret using the following command: 8. Install the driver using `csi-install.sh` bash script and default yaml by running ```bash - cd dell-csi-helm-installer && wget -O my-isilon-settings.yaml https://raw.githubusercontent.com/dell/helm-charts/csi-isilon-2.9.0/charts/csi-isilon/values.yaml && + cd dell-csi-helm-installer && wget -O my-isilon-settings.yaml https://raw.githubusercontent.com/dell/helm-charts/csi-isilon-2.9.1/charts/csi-isilon/values.yaml && ./csi-install.sh --namespace isilon --values my-isilon-settings.yaml ``` diff --git a/content/docs/csidriver/installation/helm/powerflex.md b/content/docs/csidriver/installation/helm/powerflex.md index efc95b4f93..170216c4e8 100644 --- a/content/docs/csidriver/installation/helm/powerflex.md +++ b/content/docs/csidriver/installation/helm/powerflex.md @@ -72,7 +72,7 @@ When the driver is installed using values generated by installation wizard, then ## Install the Driver **Steps** -1. Run `git clone -b v2.9.0 https://github.com/dell/csi-powerflex.git` to clone the git repository. +1. Run `git clone -b v2.9.1 https://github.com/dell/csi-powerflex.git` to clone the git repository. 2. A namespace for the driver is expected prior to running the command below. If one is not created already, you can run `kubectl create namespace vxflexos` to create a new one. Note that the namespace can be any user-defined name that follows the conventions for namespaces outlined by Kubernetes. In this example we assume that the namespace is 'vxflexos' @@ -151,7 +151,7 @@ Use the below command to replace or update the secret: 7. Download the default values.yaml file ```bash - cd dell-csi-helm-installer && wget -O myvalues.yaml https://github.com/dell/helm-charts/raw/csi-vxflexos-2.9.0/charts/csi-vxflexos/values.yaml + cd dell-csi-helm-installer && wget -O myvalues.yaml https://github.com/dell/helm-charts/raw/csi-vxflexos-2.9.1/charts/csi-vxflexos/values.yaml ``` 8. If you are using custom images, check the fields under `images` in `my-vxflexos-settings.yaml` to make sure that they are pointing to the correct image repository. @@ -160,7 +160,7 @@ Use the below command to replace or update the secret: | Parameter | Description | Required | Default | | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------- | -| version | Set to verify the values file version matches driver version and used to pull the image as part of the image name. | Yes | 2.9.0 | +| version | Set to verify the values file version matches driver version and used to pull the image as part of the image name. | Yes | 2.9.1 | | images | List all the images used by the CSI driver and CSM. If you use a private repository, change the registries accordingly. | Yes | "" | | images.powerflexSdc | Set to give the location of the SDC image used if automatic SDC deployment is being utilized. | Yes | dellemc/sdc:4.5 | | certSecretCount | Represents the number of certificate secrets, which the user is going to create for SSL authentication. | No | 0 | diff --git a/content/docs/csidriver/installation/helm/powermax.md b/content/docs/csidriver/installation/helm/powermax.md index 3711a6727b..c5213fa9a9 100644 --- a/content/docs/csidriver/installation/helm/powermax.md +++ b/content/docs/csidriver/installation/helm/powermax.md @@ -191,7 +191,7 @@ CRDs should be configured during replication prepare stage with repctl as descri **Steps** -1. Run `git clone -b v2.9.0 https://github.com/dell/csi-powermax.git` to clone the git repository. This will include the Helm charts and dell-csi-helm-installer scripts. +1. Run `git clone -b v2.9.1 https://github.com/dell/csi-powermax.git` to clone the git repository. This will include the Helm charts and dell-csi-helm-installer scripts. 2. Ensure that you have created a namespace where you want to install the driver. You can run `kubectl create namespace powermax` to create a new one 3. Edit the `samples/secret/secret.yaml` file,to point to the correct namespace, and replace the values for the username and password parameters. These values can be obtained using base64 encoding as described in the following example: @@ -206,7 +206,7 @@ CRDs should be configured during replication prepare stage with repctl as descri ``` 5. Download the default values.yaml file ```bash - cd dell-csi-helm-installer && wget -O my-powermax-settings.yaml https://github.com/dell/helm-charts/raw/csi-powermax-2.9.0/charts/csi-powermax/values.yaml + cd dell-csi-helm-installer && wget -O my-powermax-settings.yaml https://github.com/dell/helm-charts/raw/csi-powermax-2.9.1/charts/csi-powermax/values.yaml ``` 6. Ensure the unisphere have 10.0 REST endpoint support by clicking on Unisphere -> Help (?) -> About in Unisphere for PowerMax GUI. 7. Edit the newly created file and provide values for the following parameters @@ -247,7 +247,7 @@ CRDs should be configured during replication prepare stage with repctl as descri | powerMaxDebug | Enables low level and http traffic logging between the CSI driver and Unisphere. Don't enable this unless asked to do so by the support team. | No | false | | enableCHAP | Determine if the driver is going to configure SCSI node databases on the nodes with the CHAP credentials. If enabled, the CHAP secret must be provided in the credentials secret and set to the key "chapsecret" | No | false | | fsGroupPolicy | Defines which FS Group policy mode to be used, Supported modes `None, File and ReadWriteOnceWithFSType` | No | "ReadWriteOnceWithFSType" | -| version | Current version of the driver. Don't modify this value as this value will be used by the install script. | Yes | v2.9.0 | +| version | Current version of the driver. Don't modify this value as this value will be used by the install script. | Yes | v2.9.1 | | images | List all the images used by the CSI driver and CSM. If you use a private repository, change the registries accordingly. | Yes | "" || driverRepository | Defines the registry of the container image used for the driver. | Yes | dellemc | | maxPowerMaxVolumesPerNode | Specifies the maximum number of volume that can be created on a node. | Yes| 0 | | **controller** | Allows configuration of the controller-specific parameters.| - | - | diff --git a/content/docs/csidriver/installation/helm/powerstore.md b/content/docs/csidriver/installation/helm/powerstore.md index 5992e31abe..6f0b28c54c 100644 --- a/content/docs/csidriver/installation/helm/powerstore.md +++ b/content/docs/csidriver/installation/helm/powerstore.md @@ -136,7 +136,7 @@ CRDs should be configured during replication prepare stage with repctl as descri ## Install the Driver **Steps** -1. Run `git clone -b v2.9.0 https://github.com/dell/csi-powerstore.git` to clone the git repository. +1. Run `git clone -b v2.9.1 https://github.com/dell/csi-powerstore.git` to clone the git repository. 2. Ensure that you have created namespace where you want to install the driver. You can run `kubectl create namespace csi-powerstore` to create a new one. "csi-powerstore" is just an example. You can choose any name for the namespace. But make sure to align to the same namespace during the whole installation. 3. Edit `samples/secret/secret.yaml` file and configure connection information for your PowerStore arrays changing following parameters: @@ -163,7 +163,7 @@ CRDs should be configured during replication prepare stage with repctl as descri > If you do not specify `arrayID` parameter in the storage class then the array that was specified as the default would be used for provisioning volumes. 6. Download the default values.yaml file ```bash - cd dell-csi-helm-installer && wget -O my-powerstore-settings.yaml https://github.com/dell/helm-charts/raw/csi-powerstore-2.9.0/charts/csi-powerstore/values.yaml + cd dell-csi-helm-installer && wget -O my-powerstore-settings.yaml https://github.com/dell/helm-charts/raw/csi-powerstore-2.9.1/charts/csi-powerstore/values.yaml ``` 7. Edit the newly created values file and provide values for the following parameters `vi my-powerstore-settings.yaml`: diff --git a/content/docs/csidriver/installation/helm/unity.md b/content/docs/csidriver/installation/helm/unity.md index 526ecf15c9..6b9cefabdf 100644 --- a/content/docs/csidriver/installation/helm/unity.md +++ b/content/docs/csidriver/installation/helm/unity.md @@ -78,7 +78,7 @@ Install CSI Driver for Unity XT using this procedure. * As a pre-requisite for running this procedure, you must have the downloaded files, including the Helm chart from the source [git repository](https://github.com/dell/csi-unity) with the command ```bash - git clone -b v2.9.0 https://github.com/dell/csi-unity.git + git clone -b v2.9.1 https://github.com/dell/csi-unity.git ``` * In the top-level dell-csi-helm-installer directory, there should be two scripts, `csi-install.sh` and `csi-uninstall.sh`. * Ensure _unity_ namespace exists in Kubernetes cluster. Use the `kubectl create namespace unity` command to create the namespace if the namespace is not present. @@ -98,12 +98,12 @@ Procedure 2. Get the required values.yaml using the command below: ```bash -cd dell-csi-helm-installer && wget -O my-unity-settings.yaml https://github.com/dell/helm-charts/raw/csi-unity-2.9.0/charts/csi-unity/values.yaml +cd dell-csi-helm-installer && wget -O my-unity-settings.yaml https://github.com/dell/helm-charts/raw/csi-unity-2.9.1/charts/csi-unity/values.yaml ``` 3. Edit `values.yaml` to set the following parameters for your installation: - The following table lists the primary configurable parameters of the Unity XT driver chart and their default values. More detailed information can be found in the [`values.yaml`](https://github.com/dell/helm-charts/blob/csi-unity-2.9.0/charts/csi-unity/values.yaml) file in this repository. + The following table lists the primary configurable parameters of the Unity XT driver chart and their default values. More detailed information can be found in the [`values.yaml`](https://github.com/dell/helm-charts/blob/csi-unity-2.9.1/charts/csi-unity/values.yaml) file in this repository. | Parameter | Description | Required | Default | | --------- | ----------- | -------- |-------- | @@ -327,7 +327,7 @@ cd dell-csi-helm-installer && wget -O my-unity-settings.yaml https://github.com/ **Syntax**: ```bash - git clone -b csi-unity-2.9.0 https://github.com/dell/helm-charts + git clone -b csi-unity-2.9.1 https://github.com/dell/helm-charts helm install dell/container-storage-modules -n --version -f diff --git a/content/docs/csidriver/installation/offline/_index.md b/content/docs/csidriver/installation/offline/_index.md index 4e4b1b9074..4531c18e5e 100644 --- a/content/docs/csidriver/installation/offline/_index.md +++ b/content/docs/csidriver/installation/offline/_index.md @@ -83,21 +83,21 @@ bash scripts/csm-offline-bundle.sh -c * * Pulling and saving container images - dellemc/csi-isilon:v2.8.0 - dellemc/csi-metadata-retriever:v1.6.0 - dellemc/csipowermax-reverseproxy:v2.6.0 - dellemc/csi-powermax:v2.9.0 - dellemc/csi-powerstore:v2.9.0 - dellemc/csi-unity:v2.8.0 - dellemc/csi-vxflexos:v2.9.0 - dellemc/csm-authorization-sidecar:v1.9.0 + dellemc/csi-isilon:v2.9.1 + dellemc/csi-metadata-retriever:v1.6.1 + dellemc/csipowermax-reverseproxy:v2.8.1 + dellemc/csi-powermax:v2.9.1 + dellemc/csi-powerstore:v2.9.1 + dellemc/csi-unity:v2.8.1 + dellemc/csi-vxflexos:v2.9.1 + dellemc/csm-authorization-sidecar:v1.9.1 dellemc/csm-metrics-powerflex:v1.5.0 dellemc/csm-metrics-powerscale:v1.2.0 dellemc/csm-topology:v1.5.0 - dellemc/dell-csi-replicator:v1.7.0 + dellemc/dell-csi-replicator:v1.7.1 dellemc/dell-replication-controller:v1.7.0 dellemc/sdc:4.5 - docker.io/dellemc/dell-csm-operator:v1.3.0 + docker.io/dellemc/dell-csm-operator:v1.4.1 gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0 nginxinc/nginx-unprivileged:1.20 otel/opentelemetry-collector:0.42.0 @@ -186,8 +186,8 @@ Preparing a offline bundle for installation * * Loading docker images -Loaded image: docker.io/dellemc/csi-powerstore:v2.9.0 -Loaded image: docker.io/dellemc/csi-isilon:v2.8.0 +Loaded image: docker.io/dellemc/csi-powerstore:v2.9.1 +Loaded image: docker.io/dellemc/csi-isilon:v2.9.1 ... ... Loaded image: registry.k8s.io/sig-storage/csi-resizer:v1.8.0 @@ -225,4 +225,4 @@ Now that the required images are available and the Helm Charts/Operator configur *NOTES:* 1. Offline bundle installation is only supported with manual installs i.e. without using Operator Lifecycle Manager. 2. Installation should be done using the files that are obtained after unpacking the offline bundle (dell-csm-operator-bundle.tar.gz) as the image tags in the manifests are modified to point to the internal registry. -3. Offline bundle installs operator in `default` namespace via install.sh script. Make sure that the current context in kubeconfig file has the namespace set to `default`. \ No newline at end of file +3. Offline bundle installs operator in `default` namespace via install.sh script. Make sure that the current context in kubeconfig file has the namespace set to `default`. diff --git a/content/docs/csidriver/installation/test/certcsi.md b/content/docs/csidriver/installation/test/certcsi.md index 00868af30b..49f72232af 100644 --- a/content/docs/csidriver/installation/test/certcsi.md +++ b/content/docs/csidriver/installation/test/certcsi.md @@ -21,28 +21,28 @@ There are three methods of installing `cert-csi`. 1. Download the latest release of the cert-csi zip file. ```bash -curl -LO https://github.com/dell/cert-csi/releases/download/v1.3.0/cert-csi-v1.3.0.zip +curl -LO https://github.com/dell/cert-csi/releases/download/v1.3.1/cert-csi-v1.3.1.zip ``` 2. Unzip the file. ``` bash -unzip cert-csi-v1.3.0.zip -chmod +x ./cert-csi-v1.3.0 +unzip cert-csi-v1.3.1.zip +chmod +x ./cert-csi-v1.3.1 ``` -3. Install cert-csi-v1.3.0 as cert-csi. +3. Install cert-csi-v1.3.1 as cert-csi. ```bash -sudo install -o root -g root -m 0755 cert-csi-v1.3.0 /usr/local/bin/cert-csi +sudo install -o root -g root -m 0755 cert-csi-v1.3.1 /usr/local/bin/cert-csi ``` If you do not have root access on the target system, you can still install cert-csi to the ~/.local/bin directory: ```bash -chmod +x cert-csi-v1.3.0 +chmod +x cert-csi-v1.3.1 mkdir -p ~/.local/bin -mv ./cert-csi-v1.3.0 ~/.local/bin/cert-csi +mv ./cert-csi-v1.3.1 ~/.local/bin/cert-csi # and then append (or prepend) ~/.local/bin to $PATH ``` @@ -52,14 +52,14 @@ mv ./cert-csi-v1.3.0 ~/.local/bin/cert-csi {{% tab name="Docker" %}} ```bash - docker pull dellemc/cert-csi:v1.3.0 + docker pull dellemc/cert-csi:v1.3.1 ``` {{% /tab %}} {{% tab name="Podman" %}} ```bash - podman pull dellemc/cert-csi:v1.3.0 + podman pull dellemc/cert-csi:v1.3.1 ``` {{% /tab %}} @@ -74,7 +74,7 @@ mv ./cert-csi-v1.3.0 ~/.local/bin/cert-csi 1. Clone the repository ```bash -git clone -b "v1.3.0" https://github.com/dell/cert-csi.git && cd cert-csi +git clone -b "v1.3.1" https://github.com/dell/cert-csi.git && cd cert-csi ``` 2. Build cert-csi @@ -116,12 +116,12 @@ make install-ms {{% /tab %}} {{% tab name="Docker" %}} ```bash - docker run --rm -it -v ~/.kube/config:/root/.kube/config dellemc/cert-csi:v1.3.0 --help + docker run --rm -it -v ~/.kube/config:/root/.kube/config dellemc/cert-csi:v1.3.1 --help ``` {{% /tab %}} {{% tab name="Podman" %}} ```bash - podman run --rm -it -v ~/.kube/config:/root/.kube/config dellemc/cert-csi:v1.3.0 --help + podman run --rm -it -v ~/.kube/config:/root/.kube/config dellemc/cert-csi:v1.3.1 --help ``` {{% /tab %}} @@ -389,12 +389,12 @@ If you are using the container image, the `cert-config` file must be mounted int {{< tabs name="running-container-certify" >}} {{% tab name="Docker" %}} ```bash - docker run --rm -it -v ~/.kube/config:/root/.kube/config -v /home/user/example-certify-config.yaml:/example-certify-config.yaml dellemc/cert-csi:v1.3.0 certify --cert-config /example-certify-config.yaml --vsc + docker run --rm -it -v ~/.kube/config:/root/.kube/config -v /home/user/example-certify-config.yaml:/example-certify-config.yaml dellemc/cert-csi:v1.3.1 certify --cert-config /example-certify-config.yaml --vsc ``` {{% /tab %}} {{% tab name="Podman" %}} ```bash - podman run --rm -it -v ~/.kube/config:/root/.kube/config -v /home/user/example-certify-config.yaml:/example-certify-config.yaml dellemc/cert-csi:v1.3.0 certify --cert-config /example-certify-config.yaml --vsc + podman run --rm -it -v ~/.kube/config:/root/.kube/config -v /home/user/example-certify-config.yaml:/example-certify-config.yaml dellemc/cert-csi:v1.3.1 certify --cert-config /example-certify-config.yaml --vsc ``` {{% /tab %}} @@ -587,12 +587,12 @@ If you are using the container image, the `attr` file must be mounted into the c {{< tabs name="running-container-ephemeral-volume" >}} {{% tab name="Docker" %}} ```bash - docker run --rm -it -v ~/.kube/config:/root/.kube/config -v /home/user/ephemeral-config.properties:/ephemeral-config.properties dellemc/cert-csi:v1.3.0 test ephemeral-volume --driver --attr /ephemeral-config.properties + docker run --rm -it -v ~/.kube/config:/root/.kube/config -v /home/user/ephemeral-config.properties:/ephemeral-config.properties dellemc/cert-csi:v1.3.1 test ephemeral-volume --driver --attr /ephemeral-config.properties ``` {{% /tab %}} {{% tab name="Podman" %}} ```bash - podman run --rm -it -v ~/.kube/config:/root/.kube/config -v /home/user/ephemeral-config.properties:/ephemeral-config.properties dellemc/cert-csi:v1.3.0 test ephemeral-volume --driver --attr /ephemeral-config.properties + podman run --rm -it -v ~/.kube/config:/root/.kube/config -v /home/user/ephemeral-config.properties:/ephemeral-config.properties dellemc/cert-csi:v1.3.1 test ephemeral-volume --driver --attr /ephemeral-config.properties ``` {{% /tab %}} @@ -840,4 +840,4 @@ Tabular Report example ### Resource usage example chart -![img9](../img/resourceUsage.png) \ No newline at end of file +![img9](../img/resourceUsage.png) diff --git a/content/docs/csidriver/release/powerflex.md b/content/docs/csidriver/release/powerflex.md index e57a8da7ca..98fee967a6 100644 --- a/content/docs/csidriver/release/powerflex.md +++ b/content/docs/csidriver/release/powerflex.md @@ -3,7 +3,7 @@ title: PowerFlex description: Release notes for PowerFlex CSI driver --- -## Release Notes - CSI PowerFlex v2.9.0 +## Release Notes - CSI PowerFlex v2.9.1 @@ -29,6 +29,8 @@ description: Release notes for PowerFlex CSI driver - [#1057 - [BUG]: CSI Driver - issue with creation volume from 1 of the worker nodes](https://github.com/dell/csm/issues/1057) - [#1058 - [BUG]: CSI Health monitor for Node missing for CSM PowerFlex in Operator samples](https://github.com/dell/csm/issues/1058) - [#1061 - [BUG]: Golint is not installing with go get command](https://github.com/dell/csm/issues/1061) +- [#1110 - [BUG]: Multi Controller defect - sidecars timeout](https://github.com/dell/csm/issues/1110) + ### Known Issues @@ -38,10 +40,9 @@ description: Release notes for PowerFlex CSI driver | When a node goes down, the block volumes attached to the node cannot be attached to another node | This is a known issue and has been reported at https://github.com/kubernetes-csi/external-attacher/issues/215. Workaround:
1. Force delete the pod running on the node that went down
2. Delete the volumeattachment to the node that went down.
Now the volume can be attached to the new node. | | sdc:3.6.0.6 is causing issues while installing the csi-powerflex driver on ubuntu,RHEL8.3 | Workaround:
Change the powerflexSdc to sdc:3.6 in values.yaml https://github.com/dell/csi-powerflex/blob/72b27acee7553006cc09df97f85405f58478d2e4/helm/csi-vxflexos/values.yaml#L13
| | sdc:3.6.1 is causing issues while installing the csi-powerflex driver on ubuntu. | Workaround:
Change the powerflexSdc to sdc:3.6 in values.yaml https://github.com/dell/csi-powerflex/blob/72b27acee7553006cc09df97f85405f58478d2e4/helm/csi-vxflexos/values.yaml#L13
| -A CSI ephemeral pod may not get created in OpenShift 4.13 and fail with the error `"error when creating pod: the pod uses an inline volume provided by CSIDriver csi-vxflexos.dellemc.com, and the namespace has a pod security enforcement level that is lower than privileged."` | This issue occurs because OpenShift 4.13 introduced the CSI Volume Admission plugin to restrict the use of a CSI driver capable of provisioning CSI ephemeral volumes during pod admission. Therefore, an additional label `security.openshift.io/csi-ephemeral-volume-profile` in [csidriver.yaml](https://github.com/dell/helm-charts/blob/csi-vxflexos-2.9.0/charts/csi-vxflexos/templates/csidriver.yaml) file with the required security profile value should be provided. Follow [OpenShift 4.13 documentation for CSI Ephemeral Volumes](https://docs.openshift.com/container-platform/4.13/storage/container_storage_interface/ephemeral-storage-csi-inline.html) for more information. | +A CSI ephemeral pod may not get created in OpenShift 4.13 and fail with the error `"error when creating pod: the pod uses an inline volume provided by CSIDriver csi-vxflexos.dellemc.com, and the namespace has a pod security enforcement level that is lower than privileged."` | This issue occurs because OpenShift 4.13 introduced the CSI Volume Admission plugin to restrict the use of a CSI driver capable of provisioning CSI ephemeral volumes during pod admission. Therefore, an additional label `security.openshift.io/csi-ephemeral-volume-profile` in [csidriver.yaml](https://github.com/dell/helm-charts/blob/csi-vxflexos-2.9.1/charts/csi-vxflexos/templates/csidriver.yaml) file with the required security profile value should be provided. Follow [OpenShift 4.13 documentation for CSI Ephemeral Volumes](https://docs.openshift.com/container-platform/4.13/storage/container_storage_interface/ephemeral-storage-csi-inline.html) for more information. | | If the volume limit is exhausted and there are pending pods and PVCs due to `exceed max volume count`, the pending PVCs will be bound to PVs and the pending pods will be scheduled to nodes when the driver pods are restarted. | It is advised not to have any pending pods or PVCs once the volume limit per node is exhausted on a CSI Driver. There is an open issue reported with kubenetes at https://github.com/kubernetes/kubernetes/issues/95911 with the same behavior. | | The PowerFlex Dockerfile is incorrectly labeling the version as 2.7.0 for the 2.8.0 version. | Describe the driver pod using ```kubectl describe pod $podname -n vxflexos``` to ensure v2.8.0 is installed. | -| Standby controller pod is in crashloopbackoff state | Scale down the replica count of the controller pod's deployment to 1 using ```kubectl scale deployment --replicas=1 -n ``` | ### Note: diff --git a/content/docs/csidriver/release/powermax.md b/content/docs/csidriver/release/powermax.md index fc404be039..efed587b1c 100644 --- a/content/docs/csidriver/release/powermax.md +++ b/content/docs/csidriver/release/powermax.md @@ -3,7 +3,7 @@ title: PowerMax description: Release notes for PowerMax CSI driver --- -## Release Notes - CSI PowerMax v2.9.0 +## Release Notes - CSI PowerMax v2.9.1 >Note: Auto SRDF group creation is currently not supported in PowerMaxOS 10.1 (6079) Arrays. @@ -31,6 +31,8 @@ description: Release notes for PowerMax CSI driver - [#1053 - [BUG]: make gosec is erroring out - Repos PowerMax,PowerStore,PowerScale (gosec is installed)](https://github.com/dell/csm/issues/1053) - [#1056 - [BUG]: Missing runtime dependencies reference in PowerMax README file.](https://github.com/dell/csm/issues/1056) - [#1061 - [BUG]: Golint is not installing with go get command](https://github.com/dell/csm/issues/1061) +- [#1110 - [BUG]: Multi Controller defect - sidecars timeout](https://github.com/dell/csm/issues/1110) + ### Known Issues @@ -41,7 +43,6 @@ description: Release notes for PowerMax CSI driver | If the volume limit is exhausted and there are pending pods and PVCs due to `exceed max volume count`, the pending PVCs will be bound to PVs and the pending pods will be scheduled to nodes when the driver pods are restarted. | It is advised not to have any pending pods or PVCs once the volume limit per node is exhausted on a CSI Driver. There is an open issue reported with kubenetes at https://github.com/kubernetes/kubernetes/issues/95911 with the same behavior. | | Automatic SRDF group creation is failing with "Unable to get Remote Port on SAN for Auto SRDF" for PowerMaxOS 10.1 arrays | Create the SRDF Group and add it to the storage class | | [Node stage is failing with error "wwn for FC device not found"](https://github.com/dell/csm/issues/1070)| This is an intermittent issue, rebooting the node will resolve this issue | -| Standby controller pod is in crashloopbackoff state | Scale down the replica count of the controller pod's deployment to 1 using ```kubectl scale deployment --replicas=1 -n ``` | ### Note: - Support for Kubernetes alpha features like Volume Health Monitoring and RWOP (ReadWriteOncePod) access mode will not be available in Openshift environment as Openshift doesn't support enabling of alpha features for Production Grade clusters. diff --git a/content/docs/csidriver/release/powerscale.md b/content/docs/csidriver/release/powerscale.md index 8bb807be39..cc81401fd5 100644 --- a/content/docs/csidriver/release/powerscale.md +++ b/content/docs/csidriver/release/powerscale.md @@ -4,11 +4,7 @@ description: Release notes for PowerScale CSI driver --- -## Release Notes - CSI Driver for PowerScale v2.9.0 - - - - +## Release Notes - CSI Driver for PowerScale v2.9.1 ### New Features/Changes @@ -27,12 +23,13 @@ description: Release notes for PowerScale CSI driver - [#1046 - [BUG]:Is cert-csi expansion expected to successfully run with enableQuota: false on PowerScale?](https://github.com/dell/csm/issues/1046) - [#1053 - [BUG]: make gosec is erroring out - Repos PowerMax,PowerStore,PowerScale (gosec is installed)](https://github.com/dell/csm/issues/1053) - [#1061 - [BUG]: Golint is not installing with go get command](https://github.com/dell/csm/issues/1061) +- [#1110 - [BUG]: Multi Controller defect - sidecars timeout](https://github.com/dell/csm/issues/1110) ### Known Issues | Issue | Resolution or workaround, if known | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Storage capacity tracking does not return `MaximumVolumeSize` parameter. PowerScale is purely NFS based meaning it has no actual volumes. Therefore `MaximumVolumeSize` cannot be implemented if there is no volume creation. | CSI PowerScale 2.9.0 is compliant with CSI 1.6 specification since the field `MaximumVolumeSize` is optional. | +| Storage capacity tracking does not return `MaximumVolumeSize` parameter. PowerScale is purely NFS based meaning it has no actual volumes. Therefore `MaximumVolumeSize` cannot be implemented if there is no volume creation. | CSI PowerScale 2.9.1 is compliant with CSI 1.6 specification since the field `MaximumVolumeSize` is optional. | | If the length of the nodeID exceeds 128 characters, the driver fails to update the CSINode object and installation fails. This is due to a limitation set by CSI spec which doesn't allow nodeID to be greater than 128 characters. | The CSI PowerScale driver uses the hostname for building the nodeID which is set in the CSINode resource object, hence we recommend not having very long hostnames in order to avoid this issue. This current limitation of 128 characters is likely to be relaxed in future Kubernetes versions as per this issue in the community: https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/issues/581

**Note:** In kubernetes 1.22 this limit has been relaxed to 192 characters. | | If some older NFS exports /terminated worker nodes still in NFS export client list, CSI driver tries to add a new worker node it fails (For RWX volume). | User need to manually clean the export client list from old entries to make successful addition of new worker nodes. | | Delete namespace that has PVCs and pods created with the driver. The External health monitor sidecar crashes as a result of this operation. | Deleting the namespace deletes the PVCs first and then removes the pods in the namespace. This brings a condition where pods exist without their PVCs and causes the external-health-monitor sidecar to crash. This is a known issue and has been reported at https://github.com/kubernetes-csi/external-health-monitor/issues/100 | @@ -40,7 +37,6 @@ description: Release notes for PowerScale CSI driver | Driver logs shows "VendorVersion=2.3.0+dirty" | Update the driver to csi-powerscale 2.4.0 | | PowerScale 9.5.0, Driver installation fails with session based auth, "HTTP/1.1 401 Unauthorized" | Fix is available in PowerScale >= 9.5.0.4 | | If the volume limit is exhausted and there are pending pods and PVCs due to `exceed max volume count`, the pending PVCs will be bound to PVs and the pending pods will be scheduled to nodes when the driver pods are restarted. | It is advised not to have any pending pods or PVCs once the volume limit per node is exhausted on a CSI Driver. There is an open issue reported with kubenetes at https://github.com/kubernetes/kubernetes/issues/95911 with the same behavior. | -| Standby controller pod is in crashloopbackoff state | Scale down the replica count of the controller pod's deployment to 1 using ```kubectl scale deployment --replicas=1 -n ``` | ### Note diff --git a/content/docs/csidriver/release/powerstore.md b/content/docs/csidriver/release/powerstore.md index 10a8e62283..2e3e7be69d 100644 --- a/content/docs/csidriver/release/powerstore.md +++ b/content/docs/csidriver/release/powerstore.md @@ -3,11 +3,7 @@ title: PowerStore description: Release notes for PowerStore CSI driver --- -## Release Notes - CSI PowerStore v2.9.0 - - - - +## Release Notes - CSI PowerStore v2.9.1 ### New Features/Changes @@ -24,6 +20,7 @@ description: Release notes for PowerStore CSI driver - [#1014 - [BUG]: Missing error check for os.Stat call during volume publish](https://github.com/dell/csm/issues/1014) - [#1053 - [BUG]: make gosec is erroring out - Repos PowerMax,PowerStore,PowerScale (gosec is installed)](https://github.com/dell/csm/issues/1053) - [#1061 - [BUG]: Golint is not installing with go get command](https://github.com/dell/csm/issues/1061) +- [#1108 - [BUG]: Volumes failing to mount when customer using NVMeTCP on Powerstore](https://github.com/dell/csm/issues/1108) ### Known Issues diff --git a/content/docs/csidriver/release/unity.md b/content/docs/csidriver/release/unity.md index e4a451676e..530ebf0357 100644 --- a/content/docs/csidriver/release/unity.md +++ b/content/docs/csidriver/release/unity.md @@ -3,11 +3,7 @@ title: Unity XT description: Release notes for Unity XT CSI driver --- -## Release Notes - CSI Unity XT v2.9.0 - - - - +## Release Notes - CSI Unity XT v2.9.1 ### New Features/Changes @@ -20,6 +16,7 @@ description: Release notes for Unity XT CSI driver ### Fixed Issues - [#1014 - [BUG]: Missing error check for os.Stat call during volume publish](https://github.com/dell/csm/issues/1014) +- [#1110 - [BUG]: Multi Controller defect - sidecars timeout](https://github.com/dell/csm/issues/1110) ### Known Issues @@ -31,7 +28,6 @@ description: Release notes for Unity XT CSI driver | When a node goes down, the block volumes attached to the node cannot be attached to another node | This is a known issue and has been reported at https://github.com/kubernetes-csi/external-attacher/issues/215. Workaround:
1. Force delete the pod running on the node that went down
2. Delete the VolumeAttachment to the node that went down.
Now the volume can be attached to the new node. | | A CSI ephemeral pod may not get created in OpenShift 4.13 and fail with the error `"error when creating pod: the pod uses an inline volume provided by CSIDriver csi-unity.dellemc.com, and the namespace has a pod security enforcement level that is lower than privileged."` | This issue occurs because OpenShift 4.13 introduced the CSI Volume Admission plugin to restrict the use of a CSI driver capable of provisioning CSI ephemeral volumes during pod admission. Therefore, an additional label `security.openshift.io/csi-ephemeral-volume-profile` in [csidriver.yaml](https://github.com/dell/helm-charts/blob/csi-unity-2.8.0/charts/csi-unity/templates/csidriver.yaml) file with the required security profile value should be provided. Follow [OpenShift 4.13 documentation for CSI Ephemeral Volumes](https://docs.openshift.com/container-platform/4.13/storage/container_storage_interface/ephemeral-storage-csi-inline.html) for more information. | | If the volume limit is exhausted and there are pending pods and PVCs due to `exceed max volume count`, the pending PVCs will be bound to PVs and the pending pods will be scheduled to nodes when the driver pods are restarted. | It is advised not to have any pending pods or PVCs once the volume limit per node is exhausted on a CSI Driver. There is an open issue reported with kubenetes at https://github.com/kubernetes/kubernetes/issues/95911 with the same behavior. | -| Standby controller pod is in crashloopbackoff state | Scale down the replica count of the controller pod's deployment to 1 using ```kubectl scale deployment --replicas=1 -n ``` | ### Note: - Support for Kubernetes alpha features like Volume Health Monitoring and RWOP (ReadWriteOncePod) access mode will not be available in Openshift environment as Openshift doesn't support enabling of alpha features for Production Grade clusters. diff --git a/content/docs/csidriver/troubleshooting/powerflex.md b/content/docs/csidriver/troubleshooting/powerflex.md index 62d7ba0aca..0951b42c81 100644 --- a/content/docs/csidriver/troubleshooting/powerflex.md +++ b/content/docs/csidriver/troubleshooting/powerflex.md @@ -29,6 +29,7 @@ description: Troubleshooting PowerFlex Driver | In version v2.6.0, the driver is crashing because the External Health Monitor sidecar crashes when a persistent volume is not found. | This is a known issue reported at [kubernetes-csi/external-health-monitor#100](https://github.com/kubernetes-csi/external-health-monitor/issues/100). | | In version v2.6.0, when a cluster node goes down, the block volumes attached to the node cannot be attached to another node. | This is a known issue reported at [kubernetes-csi/external-attacher#215](https://github.com/kubernetes-csi/external-attacher/issues/215). Workaround:
1. Force delete the pod running on the node that went down.
2. Delete the pod's persistent volume attachment on the node that went down. Now the volume can be attached to the new node. A CSI ephemeral pod may not get created in OpenShift 4.13 and fail with the error `"error when creating pod: the pod uses an inline volume provided by CSIDriver csi-vxflexos.dellemc.com, and the namespace has a pod security enforcement level that is lower than privileged."` | This issue occurs because OpenShift 4.13 introduced the CSI Volume Admission plugin to restrict the use of a CSI driver capable of provisioning CSI ephemeral volumes during pod admission. Therefore, an additional label `security.openshift.io/csi-ephemeral-volume-profile` in [csidriver.yaml](https://github.com/dell/helm-charts/blob/csi-vxflexos-2.8.0/charts/csi-vxflexos/templates/csidriver.yaml) file with the required security profile value should be provided. Follow [OpenShift 4.13 documentation for CSI Ephemeral Volumes](https://docs.openshift.com/container-platform/4.13/storage/container_storage_interface/ephemeral-storage-csi-inline.html) for more information. | +| Standby controller pod is in crashloopbackoff state | Scale down the replica count of the controller pod's deployment to 1 using ```kubectl scale deployment --replicas=1 -n ``` | ->*Note*: `vxflexos-controller-*` is the controller pod that acquires leader lease +> diff --git a/content/docs/csidriver/troubleshooting/powermax.md b/content/docs/csidriver/troubleshooting/powermax.md index 88e61470b4..502913ef3a 100644 --- a/content/docs/csidriver/troubleshooting/powermax.md +++ b/content/docs/csidriver/troubleshooting/powermax.md @@ -18,4 +18,5 @@ description: Troubleshooting PowerMax Driver | CreateHost failed with error `initiator is already part of different host.` | Update modifyHostName to true in values.yaml Or Remove the initiator from existing host | | `kubectl logs powermax-controller- –n ` driver logs says connection refused and the reverseproxy logs says "Failed to setup server.(secrets \"secret-name\" not found)" | Make sure the given secret exist on the cluster | | nodestage is failing with error `Error invalid IQN Target iqn.EMC.0648.SE1F` | 1. Update initiator name to full default name , ex: iqn.1993-08.org.debian:01:e9afae962192
2.Ensure that the iSCSI initiators are available on all the nodes where the driver node plugin will be installed and it should be full default name. | -| Volume mount is failing on few OS(ex:VMware Virtual Platform) during node publish with error `wrong fs type, bad option, bad superblock` | 1. Check the multipath configuration(if enabled) 2. Edit Vm Advanced settings->hardware and add the param `disk.enableUUID=true` and reboot the node | +| Volume mount is failing on few OS(ex:VMware Virtual Platform) during node publish with error `wrong fs type, bad option, bad superblock` | 1. Check the multipath configuration(if enabled) 2. Edit Vm Advanced settings->hardware and add the param `disk.enableUUID=true` and reboot the node | +| Standby controller pod is in crashloopbackoff state | Scale down the replica count of the controller pod's deployment to 1 using ```kubectl scale deployment --replicas=1 -n ``` | diff --git a/content/docs/csidriver/troubleshooting/powerscale.md b/content/docs/csidriver/troubleshooting/powerscale.md index 17e3db8d90..2b57019085 100644 --- a/content/docs/csidriver/troubleshooting/powerscale.md +++ b/content/docs/csidriver/troubleshooting/powerscale.md @@ -18,3 +18,4 @@ Here are some installation failures that might be encountered and how to mitigat | The `kubectl logs isilon-controller-0 -n isilon -c driver` logs shows the driver **Authentication failed. Trying to re-authenticate** when using Session-based authentication | The issue has been resolved from OneFS 9.3 onwards, for OneFS versions prior to 9.3 for session-based authentication either smart connect can be created against a single node of Isilon or CSI Driver can be installed/pointed to a particular node of the Isilon else basic authentication can be used by setting isiAuthType in `values.yaml` to 0 | | When an attempt is made to create more than one ReadOnly PVC from the same volume snapshot, the second and subsequent requests result in PVCs in state `Pending`, with a warning `another RO volume from this snapshot is already present`. This is because the driver allows only one RO volume from a specific snapshot at any point in time. This is to allow faster creation(within a few seconds) of a RO PVC from a volume snapshot irrespective of the size of the volume snapshot. | Wait for the deletion of the first RO PVC created from the same volume snapshot. | |Driver install or upgrade fails because of an incompatible Kubernetes version, even though the version seems to be within the range of compatibility. For example: Error: UPGRADE FAILED: chart requires kubeVersion: >= 1.22.0 < 1.25.0 which is incompatible with Kubernetes V1.22.11-mirantis-1 | If you are using an extended Kubernetes version, please see the [helm Chart](https://github.com/dell/helm-charts/blob/main/charts/csi-isilon/Chart.yaml) and use the alternate kubeVersion check that is provided in the comments. Please note that this is not meant to be used to enable the use of pre-release alpha and beta versions, which is not supported.| +| Standby controller pod is in crashloopbackoff state | Scale down the replica count of the controller pod's deployment to 1 using ```kubectl scale deployment --replicas=1 -n ``` | diff --git a/content/docs/csidriver/troubleshooting/powerstore.md b/content/docs/csidriver/troubleshooting/powerstore.md index a788b011e6..9121f8c0ea 100644 --- a/content/docs/csidriver/troubleshooting/powerstore.md +++ b/content/docs/csidriver/troubleshooting/powerstore.md @@ -12,4 +12,10 @@ description: Troubleshooting PowerStore Driver | If the NVMeFC pod is not getting created and the host looses the ssh connection, causing the driver pods to go to error state | remove the nvme_tcp module from the host incase of NVMeFC connection | | When a node goes down, the block volumes attached to the node cannot be attached to another node | 1. Force delete the pod running on the node that went down
2. Delete the volumeattachment to the node that went down.
Now the volume can be attached to the new node. | | If the pod creation for NVMe takes time when the connections between the host and the array are more than 2 and considerable volumes are mounted on the host | Reduce the number of connections between the host and the array to 2. | -|Driver install or upgrade fails because of an incompatible Kubernetes version, even though the version seems to be within the range of compatibility. For example: Error: UPGRADE FAILED: chart requires kubeVersion: >= 1.22.0 < 1.25.0 which is incompatible with Kubernetes V1.22.11-mirantis-1 | If you are using an extended Kubernetes version, please see the [helm Chart](https://github.com/dell/helm-charts/blob/main/charts/csi-powerstore/Chart.yaml) and use the alternate kubeVersion check that is provided in the comments. Please note that this is not meant to be used to enable the use of pre-release alpha and beta versions, which is not supported.| \ No newline at end of file +|Driver install or upgrade fails because of an incompatible Kubernetes version, even though the version seems to be within the range of compatibility. For example: Error: UPGRADE FAILED: chart requires kubeVersion: >= 1.22.0 < 1.25.0 which is incompatible with Kubernetes V1.22.11-mirantis-1 | If you are using an extended Kubernetes version, please see the [helm Chart](https://github.com/dell/helm-charts/blob/main/charts/csi-powerstore/Chart.yaml) and use the alternate kubeVersion check that is provided in the comments. Please note that this is not meant to be used to enable the use of pre-release alpha and beta versions, which is not supported.| +| If two separate networks are configured for ISCSI and NVMeTCP, the driver may encounter difficulty identifying the second network (e.g., NVMeTCP). | This is a known issue, and the workaround involves creating a single network on the array to serve both ISCSI and NVMeTCP purposes. | +| Unable to provision PVC's via driver | Ensure that the NAS name matches the one provided on the array side. | +| Unable to install or upgrade the driver | Ensure that the firewall is configured to grant adequate permissions for downloading images from the registry. | +| Faulty paths in the multipath | Ensure that the configuration of the multipath is correct and connectivity to the underlying hardware is intact. | +| Unable to install or upgrade the driver due to minimum Kubernetes version or Openshift version | Currently CSM only supports n, n-1, n-2 version of Kubernetes and Openshift, if you still wanted to continue with existing version update the `verify.sh` to continue.| +| Volumes are not getting deleted on the array when PV's are deleted | Ensure `persistentVolumeReclaimPolicy` is set to Delete. | diff --git a/content/docs/csidriver/troubleshooting/unity.md b/content/docs/csidriver/troubleshooting/unity.md index 6a380b5754..e3a180e923 100644 --- a/content/docs/csidriver/troubleshooting/unity.md +++ b/content/docs/csidriver/troubleshooting/unity.md @@ -14,3 +14,4 @@ description: Troubleshooting Unity XT Driver | PVC creation fails on a fresh cluster with **iSCSI** and **NFS** protocols alone enabled with error **failed to provision volume with StorageClass "unity-iscsi": error generating accessibility requirements: no available topology found**. | This is because iSCSI initiator login takes longer than the node pod startup time. This can be overcome by bouncing the node pods in the cluster using the below command the driver pods with **kubectl get pods -n unity --no-headers=true \| awk '/unity-/{print $1}'\| xargs kubectl delete -n unity pod** | | Driver install or upgrade fails because of an incompatible Kubernetes version, even though the version seems to be within the range of compatibility. For example: `Error: UPGRADE FAILED: chart requires kubeVersion: >= 1.24.0 < 1.29.0 which is incompatible with Kubernetes 1.24.6-mirantis-1` | If you are using an extended Kubernetes version, see the helm Chart at `helm/csi-unity/Chart.yaml` and use the alternate `kubeVersion` check that is provided in the comments. *Note* that this is not meant to be used to enable the use of pre-release alpha and beta versions, which is not supported. | | When a node goes down, the block volumes attached to the node cannot be attached to another node | 1. Force delete the pod running on the node that went down
2. Delete the VolumeAttachment to the node that went down.
Now the volume can be attached to the new node. | +| Standby controller pod is in crashloopbackoff state | Scale down the replica count of the controller pod's deployment to 1 using ```kubectl scale deployment --replicas=1 -n ``` | diff --git a/content/docs/csidriver/upgradation/drivers/isilon.md b/content/docs/csidriver/upgradation/drivers/isilon.md index 300fbec728..b278408360 100644 --- a/content/docs/csidriver/upgradation/drivers/isilon.md +++ b/content/docs/csidriver/upgradation/drivers/isilon.md @@ -8,19 +8,19 @@ Description: Upgrade PowerScale CSI driver --- You can upgrade the CSI Driver for Dell PowerScale using Helm or Dell CSM Operator. -## Upgrade Driver from version 2.8.0 to 2.9.0 using Helm +## Upgrade Driver from version 2.8.0 to 2.9.1 using Helm **Note:** While upgrading the driver via helm, controllerCount variable in myvalues.yaml can be at most one less than the number of worker nodes. ### Steps -1. Clone the repository using `git clone -b v2.9.0 https://github.com/dell/csi-powerscale.git` +1. Clone the repository using `git clone -b v2.9.1 https://github.com/dell/csi-powerscale.git` 2. Change to directory dell-csi-helm-installer to install the Dell PowerScale `cd dell-csi-helm-installer` 3. Download the default values.yaml using following command: ```bash - wget -O my-isilon-settings.yaml https://raw.githubusercontent.com/dell/helm-charts/csi-isilon-2.9.0/charts/csi-isilon/values.yaml + wget -O my-isilon-settings.yaml https://raw.githubusercontent.com/dell/helm-charts/csi-isilon-2.9.1/charts/csi-isilon/values.yaml ``` Edit the _my-isilon-settings.yaml_ as per the requirements. diff --git a/content/docs/csidriver/upgradation/drivers/powerflex.md b/content/docs/csidriver/upgradation/drivers/powerflex.md index f7ec33ffe7..43c4f333af 100644 --- a/content/docs/csidriver/upgradation/drivers/powerflex.md +++ b/content/docs/csidriver/upgradation/drivers/powerflex.md @@ -10,9 +10,9 @@ Description: Upgrade PowerFlex CSI driver You can upgrade the CSI Driver for Dell PowerFlex using Helm or Dell CSM Operator. -## Update Driver from v2.8.0 to v2.9.0 using Helm +## Update Driver from v2.8.0 to v2.9.1 using Helm **Steps** -1. Run `git clone -b v2.9.0 https://github.com/dell/csi-powerflex.git` to clone the git repository and get the v2.9.0 driver. +1. Run `git clone -b v2.9.1 https://github.com/dell/csi-powerflex.git` to clone the git repository and get the v2.9.1 driver. 2. You need to create secret.yaml with the configuration of your system. Check this section in installation documentation: [Install the Driver](../../../installation/helm/powerflex#install-the-driver) 3. Update myvalues file as needed. diff --git a/content/docs/csidriver/upgradation/drivers/powermax.md b/content/docs/csidriver/upgradation/drivers/powermax.md index cf516f7178..e76bb61eb2 100644 --- a/content/docs/csidriver/upgradation/drivers/powermax.md +++ b/content/docs/csidriver/upgradation/drivers/powermax.md @@ -16,10 +16,10 @@ You can upgrade CSI Driver for Dell PowerMax using Helm or Dell CSM Operator. 1. Upgrade the Unisphere to have 10.0 endpoint support.Please find the instructions [here.](https://dl.dell.com/content/manual34878027-dell-unisphere-for-powermax-10-0-0-installation-guide.pdf?language=en-us&ps=true) 2. Update the `my-powermax-settings.yaml` to have endpoint with 10.0 support. -## Update Driver from v2.8 to v2.9 using Helm +## Update Driver from v2.8 to v2.9.1 using Helm **Steps** -1. Run `git clone -b v2.9.0 https://github.com/dell/csi-powermax.git` to clone the git repository and get the driver. +1. Run `git clone -b v2.9.1 https://github.com/dell/csi-powermax.git` to clone the git repository and get the driver. 2. Update the values file as needed. 3. Run the `csi-install` script with the option _\-\-upgrade_ by running: ```bash diff --git a/content/docs/csidriver/upgradation/drivers/powerstore.md b/content/docs/csidriver/upgradation/drivers/powerstore.md index b1bddc435c..28204eaa21 100644 --- a/content/docs/csidriver/upgradation/drivers/powerstore.md +++ b/content/docs/csidriver/upgradation/drivers/powerstore.md @@ -9,12 +9,12 @@ Description: Upgrade PowerStore CSI driver You can upgrade the CSI Driver for Dell PowerStore using Helm. -## Update Driver from v2.8.0 to v2.9.0 using Helm +## Update Driver from v2.8.0 to v2.9.1 using Helm Note: While upgrading the driver via helm, controllerCount variable in myvalues.yaml can be at most one less than the number of worker nodes. **Steps** -1. Run `git clone -b v2.9.0 https://github.com/dell/csi-powerstore.git` to clone the git repository and get the driver. +1. Run `git clone -b v2.9.1 https://github.com/dell/csi-powerstore.git` to clone the git repository and get the driver. 2. Edit `samples/secret/secret.yaml` file and configure connection information for your PowerStore arrays changing the following parameters: - *endpoint*: defines the full URL path to the PowerStore API. - *globalID*: specifies what storage cluster the driver should use @@ -38,7 +38,7 @@ Note: While upgrading the driver via helm, controllerCount variable in myvalues. kubectl create secret generic powerstore-config -n csi-powerstore --from-file=config=secret.yaml ``` -5. Download the default values.yaml file `cd dell-csi-helm-installer && wget -O my-powerstore-settings.yaml https://github.com/dell/helm-charts/raw/csi-powerstore-2.9.0/charts/csi-powerstore/values.yaml` and update parameters as per the requirement. +5. Download the default values.yaml file `cd dell-csi-helm-installer && wget -O my-powerstore-settings.yaml https://github.com/dell/helm-charts/raw/csi-powerstore-2.9.1/charts/csi-powerstore/values.yaml` and update parameters as per the requirement. 6. Run the `csi-install` script with the option _\-\-upgrade_ by running: ```bash diff --git a/content/docs/csidriver/upgradation/drivers/unity.md b/content/docs/csidriver/upgradation/drivers/unity.md index 3f0422ef2b..3b8c0108d9 100644 --- a/content/docs/csidriver/upgradation/drivers/unity.md +++ b/content/docs/csidriver/upgradation/drivers/unity.md @@ -20,9 +20,9 @@ You can upgrade the CSI Driver for Dell Unity XT using Helm or Dell CSM Operator Preparing myvalues.yaml is the same as explained in the install section. -To upgrade the driver from csi-unity v2.8.0 to csi-unity v2.9.0 +To upgrade the driver from csi-unity v2.8.0 to csi-unity v2.9.1 -1. Get the latest csi-unity v2.9.0 code from Github using `git clone -b v2.9.0 https://github.com/dell/csi-unity.git`. +1. Get the latest csi-unity v2.9.1 code from Github using `git clone -b v2.9.1 https://github.com/dell/csi-unity.git`. 2. Copy the helm/csi-unity/values.yaml to the new location csi-unity/dell-csi-helm-installer and rename it to myvalues.yaml. Customize settings for installation by editing myvalues.yaml as needed. 3. Navigate to csi-unity/dell-csi-hem-installer folder and execute this command: ```bash diff --git a/content/docs/deployment/csminstallationwizard/_index.md b/content/docs/deployment/csminstallationwizard/_index.md index 877bddf150..ad5c047b52 100644 --- a/content/docs/deployment/csminstallationwizard/_index.md +++ b/content/docs/deployment/csminstallationwizard/_index.md @@ -13,19 +13,19 @@ The [Dell Container Storage Modules Installation Wizard](./src/index.html) is a | CSI Driver | Version | Helm | Operator | | ------------------ | --------- | ------ | --------- | -| CSI PowerStore | 2.9.0 |✔️ |✔️ | +| CSI PowerStore | 2.9.1 |✔️ |✔️ | | CSI PowerStore | 2.8.0 |✔️ |✔️ | | CSI PowerStore | 2.7.0 |✔️ |✔️ | -| CSI PowerMax | 2.9.0 |✔️ |✔️ | +| CSI PowerMax | 2.9.1 |✔️ |✔️ | | CSI PowerMax | 2.8.0 |✔️ |✔️ | | CSI PowerMax | 2.7.0 |✔️ |✔️ | -| CSI PowerFlex | 2.9.0 |✔️ |❌ | +| CSI PowerFlex | 2.9.1 |✔️ |❌ | | CSI PowerFlex | 2.8.0 |✔️ |❌ | | CSI PowerFlex | 2.7.0 |✔️ |❌ | -| CSI PowerScale | 2.9.0 |✔️ |✔️ | +| CSI PowerScale | 2.9.1 |✔️ |✔️ | | CSI PowerScale | 2.8.0 |✔️ |✔️ | | CSI PowerScale | 2.7.0 |✔️ |✔️ | -| CSI Unity XT | 2.9.0 |✔️ |❌ | +| CSI Unity XT | 2.9.1 |✔️ |❌ | | CSI Unity XT | 2.8.0 |✔️ |❌ | | CSI Unity XT | 2.7.0 |✔️ |❌ | @@ -36,8 +36,8 @@ The [Dell Container Storage Modules Installation Wizard](./src/index.html) is a | CSM Modules | Version | | ---------------------| --------- | | CSM Observability | 1.7.0 | -| CSM Replication | 1.7.0 | -| CSM Resiliency | 1.7.0 | +| CSM Replication | 1.7.1 | +| CSM Resiliency | 1.8.1 | ## Installation @@ -97,7 +97,7 @@ The [Dell Container Storage Modules Installation Wizard](./src/index.html) is a ```terminal helm install dell/container-storage-modules -n --version -f - Example: helm install powerstore dell/container-storage-modules -n csi-powerstore --version 1.1.0 -f values.yaml + Example: helm install powerstore dell/container-storage-modules -n csi-powerstore --version 1.2.1 -f values.yaml ``` ## Installation Using Operator diff --git a/content/docs/deployment/csminstallationwizard/release/_index.md b/content/docs/deployment/csminstallationwizard/release/_index.md index bd688a4343..eb9869453a 100644 --- a/content/docs/deployment/csminstallationwizard/release/_index.md +++ b/content/docs/deployment/csminstallationwizard/release/_index.md @@ -5,7 +5,7 @@ weight: 5 description: Release notes for CSM Installation Wizard --- -## Release Notes - CSM Installation Wizard 1.1.0 +## Release Notes - CSM Installation Wizard 1.2.1 diff --git a/content/docs/deployment/csminstallationwizard/src/index.html b/content/docs/deployment/csminstallationwizard/src/index.html index a277c16752..463c17647c 100644 --- a/content/docs/deployment/csminstallationwizard/src/index.html +++ b/content/docs/deployment/csminstallationwizard/src/index.html @@ -87,7 +87,7 @@ diff --git a/content/docs/deployment/csminstallationwizard/src/static/js/constants.js b/content/docs/deployment/csminstallationwizard/src/static/js/constants.js index 7245d6e51b..b7396db8d7 100644 --- a/content/docs/deployment/csminstallationwizard/src/static/js/constants.js +++ b/content/docs/deployment/csminstallationwizard/src/static/js/constants.js @@ -42,7 +42,7 @@ const CONSTANTS = { OPERATOR: "operator", CSM_HELM_V170: "1.0.0", CSM_HELM_V180: "1.1.0", - CSM_HELM_V190: "1.2.0", + CSM_HELM_V191: "1.2.1", HELM_TAINTS: ` - key: "$KEY" operator: "Exists" diff --git a/content/docs/deployment/csminstallationwizard/src/static/js/ui-functions.js b/content/docs/deployment/csminstallationwizard/src/static/js/ui-functions.js index 4298b77eca..3c05ed39b2 100644 --- a/content/docs/deployment/csminstallationwizard/src/static/js/ui-functions.js +++ b/content/docs/deployment/csminstallationwizard/src/static/js/ui-functions.js @@ -478,11 +478,11 @@ function displayCommands(releaseNameValue, commandTitleValue, commandNoteValue, case "1.8.0": helmChartVersion = CONSTANTS.CSM_HELM_V180; break; - case "1.9.0": - helmChartVersion = CONSTANTS.CSM_HELM_V190; + case "1.9.1": + helmChartVersion = CONSTANTS.CSM_HELM_V191; break; default: - helmChartVersion = CONSTANTS.CSM_HELM_V190; + helmChartVersion = CONSTANTS.CSM_HELM_V191; break; } $("#command-text-area").show(); diff --git a/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.9.0-values.template b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.9.1-values.template similarity index 93% rename from content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.9.0-values.template rename to content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.9.1-values.template index 826efc7f15..133bf21686 100644 --- a/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.9.0-values.template +++ b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.9.1-values.template @@ -4,10 +4,10 @@ ########################################## csi-powerstore: enabled: $POWERSTORE_ENABLED - version: v2.9.0 + version: v2.9.1 images: # "driver" defines the container image, used for the driver container. - driver: dellemc/csi-powerstore:v2.9.0 + driver: dellemc/csi-powerstore:v2.9.1 # CSI sidecars attacher: registry.k8s.io/sig-storage/csi-attacher:v4.4.2 provisioner: registry.k8s.io/sig-storage/csi-provisioner:v3.6.2 @@ -17,10 +17,10 @@ csi-powerstore: healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.10.0 # CSM sidecars - replication: dellemc/dell-csi-replicator:v1.7.0 + replication: dellemc/dell-csi-replicator:v1.7.1 vgsnapshotter: dellemc/csi-volumegroup-snapshotter:v1.4.0 - podmon: dellemc/podmon:v1.8.0 - metadataretriever: dellemc/csi-metadata-retriever:v1.6.0 + podmon: dellemc/podmon:v1.8.1 + metadataretriever: dellemc/csi-metadata-retriever:v1.6.1 ## Controller ATTRIBUTES controller: controllerCount: $CONTROLLER_COUNT @@ -90,10 +90,10 @@ csi-powermax: managementServers: - endpoint: $POWERMAX_MANAGEMENT_SERVERS_ENDPOINT_URL - endpoint: $TARGET_UNISPHERE - version: v2.9.0 + version: v2.9.1 images: # "driver" defines the container image, used for the driver container. - driver: dellemc/csi-powermax:v2.9.0 + driver: dellemc/csi-powermax:v2.9.1 csireverseproxy: dellemc/csipowermax-reverseproxy:v2.8.0 # CSI sidecars attacher: registry.k8s.io/sig-storage/csi-attacher:v4.4.2 @@ -103,8 +103,8 @@ csi-powermax: registrar: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.9.1 healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.10.0 # CSM sidecars - replication: dellemc/dell-csi-replicator:v1.7.0 - authorization: dellemc/csm-authorization-sidecar:v1.9.0 + replication: dellemc/dell-csi-replicator:v1.7.1 + authorization: dellemc/csm-authorization-sidecar:v1.9.1 migration: dellemc/dell-csi-migrator:v1.3.0 noderescan: dellemc/dell-csi-node-rescanner:v1.2.0 clusterPrefix: $POWERMAX_CLUSTER_PREFIX @@ -166,10 +166,10 @@ csi-powermax: ########################################## csi-vxflexos: enabled: $POWERFLEX_ENABLED - version: v2.9.0 + version: v2.9.1 images: # "driver" defines the container image, used for the driver container. - driver: dellemc/csi-vxflexos:v2.9.0 + driver: dellemc/csi-vxflexos:v2.9.1 # "powerflexSdc" defines the SDC image for init container. powerflexSdc: dellemc/sdc:4.5 # CSI sidecars @@ -180,10 +180,10 @@ csi-vxflexos: registrar: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.9.1 healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.10.0 # CSM sidecars - replication: dellemc/dell-csi-replicator:v1.7.0 + replication: dellemc/dell-csi-replicator:v1.7.1 vgsnapshotter: dellemc/csi-volumegroup-snapshotter:v1.4.0 - podmon: dellemc/podmon:v1.8.0 - authorization: dellemc/csm-authorization-sidecar:v1.9.0 + podmon: dellemc/podmon:v1.8.1 + authorization: dellemc/csm-authorization-sidecar:v1.9.1 certSecretCount: $CERT_SECRET_COUNT controller: replication: @@ -247,10 +247,10 @@ csi-vxflexos: ########################################## csi-isilon: enabled: $POWERSCALE_ENABLED - version: "v2.9.0" + version: "v2.9.1" images: # "driver" defines the container image, used for the driver container. - driver: dellemc/csi-isilon:v2.9.0 + driver: dellemc/csi-isilon:v2.9.1 # CSI sidecars attacher: registry.k8s.io/sig-storage/csi-attacher:v4.4.2 provisioner: registry.k8s.io/sig-storage/csi-provisioner:v3.6.2 @@ -259,10 +259,10 @@ csi-isilon: registrar: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.9.1 healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.10.0 # CSM sidecars - replication: dellemc/dell-csi-replicator:v1.7.0 - podmon: dellemc/podmon:v1.8.0 - authorization: dellemc/csm-authorization-sidecar:v1.9.0 - metadataretriever: dellemc/csi-metadata-retriever:v1.4.0 + replication: dellemc/dell-csi-replicator:v1.7.1 + podmon: dellemc/podmon:v1.8.1 + authorization: dellemc/csm-authorization-sidecar:v1.9.1 + metadataretriever: dellemc/csi-metadata-retriever:v1.6.1 encryption: dellemc/csm-encryption:v0.3.0 certSecretCount: $CERT_SECRET_COUNT @@ -333,10 +333,10 @@ csi-isilon: ########################################## csi-unity: enabled: $UNITY_ENABLED - version: v2.9.0 + version: v2.9.1 images: # "driver" defines the container image, used for the driver container. - driver: dellemc/csi-unity:v2.9.0 + driver: dellemc/csi-unity:v2.9.1 # CSI sidecars attacher: registry.k8s.io/sig-storage/csi-attacher:v4.4.0 provisioner: registry.k8s.io/sig-storage/csi-provisioner:v3.6.0 @@ -345,7 +345,7 @@ csi-unity: registrar: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.9.0 healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.10.0 # CSM sidecars - podmon: dellemc/podmon:v1.8.0 + podmon: dellemc/podmon:v1.8.1 certSecretCount: $CERT_SECRET_COUNT fsGroupPolicy: $FSGROUP_POLICY controller: diff --git a/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-isilon-1.9.0.template b/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-isilon-1.9.1.template similarity index 98% rename from content/docs/deployment/csminstallationwizard/src/templates/operator/csm-isilon-1.9.0.template rename to content/docs/deployment/csminstallationwizard/src/templates/operator/csm-isilon-1.9.1.template index 2cb6f220f9..640bd19eab 100644 --- a/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-isilon-1.9.0.template +++ b/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-isilon-1.9.1.template @@ -16,16 +16,16 @@ spec: # true: enable storage capacity tracking # false: disable storage capacity tracking storageCapacity: $STORAGE_CAPACITY_ENABLED - # Config version for CSI PowerScale v2.9.0 driver - configVersion: v2.9.0 + # Config version for CSI PowerScale v2.9.1 driver + configVersion: v2.9.1 authSecret: isilon-creds replicas: $CONTROLLER_COUNT dnsPolicy: ClusterFirstWithHostNet # Uninstall CSI Driver and/or modules when CR is deleted forceRemoveDriver: true common: - # Image for CSI PowerScale driver v2.9.0 - image: "dellemc/csi-isilon:v2.9.0" + # Image for CSI PowerScale driver v2.9.1 + image: "dellemc/csi-isilon:v2.9.1" imagePullPolicy: IfNotPresent envs: # X_CSI_VERBOSE: Indicates what content of the OneFS REST API message should be logged in debug level logs @@ -245,10 +245,10 @@ spec: - name: authorization # enable: Enable/Disable csm-authorization enabled: $AUTHORIZATION_ENABLED - configVersion: v1.9.0 + configVersion: v1.9.1 components: - name: karavi-authorization-proxy - image: dellemc/csm-authorization-sidecar:v1.9.0 + image: dellemc/csm-authorization-sidecar:v1.9.1 envs: # proxyHost: hostname of the csm-authorization server - name: "PROXY_HOST" @@ -267,13 +267,13 @@ spec: # false: disable replication feature(do not install dell-csi-replicator sidecar) # Default value: false enabled: $REPLICATION_ENABLED - configVersion: v1.7.0 + configVersion: v1.7.1 components: - name: dell-csi-replicator # image: Image to use for dell-csi-replicator. This shouldn't be changed # Allowed values: string # Default value: None - image: dellemc/dell-csi-replicator:v1.7.0 + image: dellemc/dell-csi-replicator:v1.7.1 envs: # replicationPrefix: prefix to prepend to storage classes parameters # Allowed values: string @@ -289,7 +289,7 @@ spec: - name: dell-replication-controller-manager # image: Defines controller image. This shouldn't be changed # Allowed values: string - image: dellemc/dell-replication-controller:v1.7.0 + image: dellemc/dell-replication-controller:v1.7.1 envs: # TARGET_CLUSTERS_IDS: comma separated list of cluster IDs of the targets clusters. DO NOT include the source(wherever CSM Operator is deployed) cluster ID # Set the value to "self" in case of stretched/single cluster configuration diff --git a/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.9.0.template b/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.9.1.template similarity index 97% rename from content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.9.0.template rename to content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.9.1.template index b083f903fe..12c8970422 100644 --- a/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.9.0.template +++ b/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.9.1.template @@ -31,8 +31,8 @@ spec: # true: enable storage capacity tracking # false: disable storage capacity tracking storageCapacity: $STORAGE_CAPACITY_ENABLED - # Config version for CSI PowerMax v2.9.0 driver - configVersion: v2.9.0 + # Config version for CSI PowerMax v2.9.1 driver + configVersion: v2.9.1 # replica: Define the number of PowerMax controller nodes # to deploy to the Kubernetes release # Allowed values: n, where n > 0 @@ -44,8 +44,8 @@ spec: forceUpdate: false forceRemoveDriver: true common: - # Image for CSI PowerMax driver v2.9.0 - image: dellemc/csi-powermax:v2.9.0 + # Image for CSI PowerMax driver v2.9.1 + image: dellemc/csi-powermax:v2.9.1 # imagePullPolicy: Policy to determine if the image should be pulled prior to starting the container. # Allowed values: # Always: Always pull the image. @@ -232,14 +232,14 @@ spec: - name: csireverseproxy # enabled: Always set to true enabled: true - configVersion: v2.8.0 + configVersion: v2.8.1 forceRemoveModule: true components: - name: csipowermax-reverseproxy # image: Define the container images used for the reverse proxy # Default value: None # Example: "csipowermax-reverseproxy:v2.8.0" - image: dellemc/csipowermax-reverseproxy:v2.8.0 + image: dellemc/csipowermax-reverseproxy:v2.8.1 envs: # "tlsSecret" defines the TLS secret that is created with certificate # and its associated key @@ -256,10 +256,10 @@ spec: - name: authorization # enabled: Enable/Disable csm-authorization enabled: $AUTHORIZATION_ENABLED - configVersion: v1.9.0 + configVersion: v1.9.1 components: - name: karavi-authorization-proxy - image: dellemc/csm-authorization-sidecar:v1.9.0 + image: dellemc/csm-authorization-sidecar:v1.9.1 envs: # proxyHost: hostname of the csm-authorization server - name: "PROXY_HOST" @@ -277,13 +277,13 @@ spec: # false: disable replication feature(do not install dell-csi-replicator sidecar) # Default value: false enabled: $REPLICATION_ENABLED - configVersion: v1.7.0 + configVersion: v1.7.1 components: - name: dell-csi-replicator # image: Image to use for dell-csi-replicator. This shouldn't be changed # Allowed values: string # Default value: None - image: dellemc/dell-csi-replicator:v1.7.0 + image: dellemc/dell-csi-replicator:v1.7.1 envs: # replicationPrefix: prefix to prepend to storage classes parameters # Allowed values: string @@ -299,7 +299,7 @@ spec: - name: dell-replication-controller-manager # image: Defines controller image. This shouldn't be changed # Allowed values: string - image: dellemc/dell-replication-controller:v1.7.0 + image: dellemc/dell-replication-controller:v1.7.1 envs: # TARGET_CLUSTERS_IDS: comma separated list of cluster IDs of the targets clusters. DO NOT include the source(wherever CSM Operator is deployed) cluster ID # Set the value to "self" in case of stretched/single cluster configuration diff --git a/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powerstore-1.9.0.template b/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powerstore-1.9.1.template similarity index 96% rename from content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powerstore-1.9.0.template rename to content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powerstore-1.9.1.template index 11535b5d19..ec074e85c1 100644 --- a/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powerstore-1.9.0.template +++ b/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powerstore-1.9.1.template @@ -31,8 +31,8 @@ spec: # true: enable storage capacity tracking # false: disable storage capacity tracking storageCapacity: $STORAGE_CAPACITY_ENABLED - # Config version for CSI PowerStore v2.9.0 driver - configVersion: v2.9.0 + # Config version for CSI PowerStore v2.9.1 driver + configVersion: v2.9.1 # authSecret: This is the secret used to validate the default PowerStore secret used for installation # Allowed values: -config # For example: If the metadataName is set to powerstore, authSecret value should be set to powerstore-config @@ -43,8 +43,8 @@ spec: forceUpdate: false forceRemoveDriver: true common: - # Image for CSI PowerStore driver v2.9.0 - image: "dellemc/csi-powerstore:v2.9.0" + # Image for CSI PowerStore driver v2.9.1 + image: "dellemc/csi-powerstore:v2.9.1" imagePullPolicy: IfNotPresent envs: - name: X_CSI_POWERSTORE_NODE_NAME_PREFIX @@ -156,10 +156,10 @@ spec: # false: disable Resiliency feature(do not deploy podmon sidecar) # Default value: false enabled: $OPERATOR_RESILIENCY_ENABLED - configVersion: v1.8.0 + configVersion: v1.8.1 components: - name: podmon-controller - image: dellemc/podmon:v1.8.0 + image: dellemc/podmon:v1.8.1 imagePullPolicy: IfNotPresent args: - "--labelvalue=$LABEL_VALUE" @@ -174,7 +174,7 @@ spec: - "--driver-config-params=/powerstore-config-params/driver-config-params.yaml" - "--driverPath=csi-powerstore.dellemc.com" - name: podmon-node - image: dellemc/podmon:v1.8.0 + image: dellemc/podmon:v1.8.1 imagePullPolicy: IfNotPresent envs: # podmonAPIPort: Defines the port to be used within the kubernetes cluster diff --git a/content/docs/deployment/csmoperator/_index.md b/content/docs/deployment/csmoperator/_index.md index 73d89aee03..b5b6731e22 100644 --- a/content/docs/deployment/csmoperator/_index.md +++ b/content/docs/deployment/csmoperator/_index.md @@ -24,19 +24,19 @@ The table below lists the driver and modules versions installable with the CSM O | CSI Driver | Version | CSM Authorization | CSM Replication | CSM Observability | CSM Resiliency | | ------------------ |---------|-------------------|-----------------|-------------------|----------------| -| CSI PowerScale | 2.9.0 | ✔ 1.9.0 | ✔ 1.7.0 | ✔ 1.7.0 | ✔ 1.8.0 | +| CSI PowerScale | 2.9.1 | ✔ 1.9.1 | ✔ 1.7.1 | ✔ 1.7.0 | ✔ 1.8.1 | | CSI PowerScale | 2.8.0 | ✔ 1.8.0 | ✔ 1.6.0 | ✔ 1.6.0 | ✔ 1.7.0 | | CSI PowerScale | 2.7.0 | ✔ 1.7.0 | ✔ 1.5.0 | ✔ 1.5.0 | ✔ 1.6.0 | -| CSI PowerFlex | 2.9.0 | ✔ 1.9.0 | ✔ 1.7.0 | ✔ 1.7.0 | ✔ 1.8.0 | +| CSI PowerFlex | 2.9.1 | ✔ 1.9.1 | ✔ 1.7.1 | ✔ 1.7.0 | ✔ 1.8.1 | | CSI PowerFlex | 2.8.0 | ✔ 1.8.0 | ✔ 1.6.0 | ✔ 1.6.0 | ✔ 1.7.0 | | CSI PowerFlex | 2.7.0 | ✔ 1.7.0 | ✔ 1.5.0 | ✔ 1.5.0 | ✔ 1.6.0 | -| CSI PowerStore | 2.9.0 | ❌ | ❌ | ❌ | ✔ 1.8.0 | +| CSI PowerStore | 2.9.1 | ❌ | ❌ | ❌ | ✔ 1.8.0 | | CSI PowerStore | 2.8.0 | ❌ | ❌ | ❌ | ✔ 1.7.0 | | CSI PowerStore | 2.7.0 | ❌ | ❌ | ❌ | ✔ 1.6.0 | -| CSI PowerMax | 2.9.0 | ✔ 1.9.0 | ✔ 1.7.0 | ✔ 1.7.0 | ❌ | +| CSI PowerMax | 2.9.1 | ✔ 1.9.1 | ✔ 1.7.1 | ✔ 1.7.0 | ❌ | | CSI PowerMax | 2.8.0 | ✔ 1.8.0 | ✔ 1.6.0 | ✔ 1.6.0 | ❌ | | CSI PowerMax | 2.7.0 | ✔ 1.7.0 | ✔ 1.5.0 | ❌ | ❌ | -| CSI Unity XT | 2.9.0 | ❌ | ❌ | ❌ | ❌ | +| CSI Unity XT | 2.9.1 | ❌ | ❌ | ❌ | ❌ | | CSI Unity XT | 2.8.0 | ❌ | ❌ | ❌ | ❌ | | CSI Unity XT | 2.7.0 | ❌ | ❌ | ❌ | ❌ | @@ -64,7 +64,7 @@ The installation process involves the creation of a `Subscription` object either 1. Install volume snapshot CRDs. For detailed snapshot setup procedure, [click here](../../snapshots/#volume-snapshot-feature). 2. Clone and checkout the required csm-operator version using ```bash -git clone -b v1.4.0 https://github.com/dell/csm-operator.git +git clone -b v1.4.1 https://github.com/dell/csm-operator.git ``` 3. `cd csm-operator` 4. _(Optional)_ If using a local Docker image, edit the `deploy/operator.yaml` file and set the image name for the CSM Operator Deployment. @@ -136,7 +136,7 @@ This needs to be performed on a Linux system with access to the Internet as a gi To build an offline bundle, the following steps are needed: 1. Clone and checkout the required csm-operator version using ```bash -git clone -b v1.4.0 https://github.com/dell/csm-operator.git +git clone -b v1.4.1 https://github.com/dell/csm-operator.git ``` 2. `cd csm-operator` 3. Run the `csm-offline-bundle.sh` script which will be found in the `scripts` directory with an argument of `-c` in order to create an offline bundle @@ -161,21 +161,21 @@ Here is the output of a request to build an offline bundle for the Dell CSM Oper * * Pulling and saving container images - dellemc/csi-isilon:v2.9.0 - dellemc/csi-metadata-retriever:v1.6.0 - dellemc/csipowermax-reverseproxy:v2.8.0 - dellemc/csi-powermax:v2.9.0 - dellemc/csi-powerstore:v2.9.0 - dellemc/csi-unity:v2.9.0 - dellemc/csi-vxflexos:v2.9.0 - dellemc/csm-authorization-sidecar:v1.9.0 + dellemc/csi-isilon:v2.9.1 + dellemc/csi-metadata-retriever:v1.6.1 + dellemc/csipowermax-reverseproxy:v2.8.1 + dellemc/csi-powermax:v2.9.1 + dellemc/csi-powerstore:v2.9.1 + dellemc/csi-unity:v2.9.1 + dellemc/csi-vxflexos:v2.9.1 + dellemc/csm-authorization-sidecar:v1.9.1 dellemc/csm-metrics-powerflex:v1.7.0 dellemc/csm-metrics-powerscale:v1.4.0 dellemc/csm-topology:v1.7.0 dellemc/dell-csi-replicator:v1.7.0 dellemc/dell-replication-controller:v1.7.0 dellemc/sdc:4.5 - docker.io/dellemc/dell-csm-operator:v1.4.0 + docker.io/dellemc/dell-csm-operator:v1.4.1 gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0 nginxinc/nginx-unprivileged:1.20 otel/opentelemetry-collector:0.42.0 @@ -265,8 +265,8 @@ Preparing a offline bundle for installation * * Loading docker images -Loaded image: docker.io/dellemc/csi-powerstore:v2.9.0 -Loaded image: docker.io/dellemc/csi-isilon:v2.9.0 +Loaded image: docker.io/dellemc/csi-powerstore:v2.9.1 +Loaded image: docker.io/dellemc/csi-isilon:v2.9.1 ... ... Loaded image: registry.k8s.io/sig-storage/csi-resizer:v1.9.2 @@ -275,7 +275,7 @@ Loaded image: registry.k8s.io/sig-storage/csi-snapshotter:v6.3.2 * * Tagging and pushing images - dellemc/csi-isilon:v2.9.0 -> localregistry:5000/dell-csm-operator/csi-isilon:v2.9.0 + dellemc/csi-isilon:v2.9.1 -> localregistry:5000/dell-csm-operator/csi-isilon:v2.9.1 dellemc/csi-metadata-retriever:v1.6.0 -> localregistry:5000/dell-csm-operator/csi-metadata-retriever:v1.6.0 ... ... @@ -285,8 +285,8 @@ Loaded image: registry.k8s.io/sig-storage/csi-snapshotter:v6.3.2 * * Preparing files within /root/dell-csm-operator-bundle - changing: dellemc/csi-isilon:v2.9.0 -> localregistry:5000/dell-csm-operator/csi-isilon:v2.9.0 - changing: dellemc/csi-metadata-retriever:v1.6.0 -> localregistry:5000/dell-csm-operator/csi-metadata-retriever:v1.6.0 + changing: dellemc/csi-isilon:v2.9.1 -> localregistry:5000/dell-csm-operator/csi-isilon:v2.9.1 + changing: dellemc/csi-metadata-retriever:v1.6.1 -> localregistry:5000/dell-csm-operator/csi-metadata-retriever:v1.6.1 ... ... changing: registry.k8s.io/sig-storage/csi-resizer:v1.9.2 -> localregistry:5000/dell-csm-operator/csi-resizer:v1.9.2 @@ -342,7 +342,7 @@ The `Update approval` (**`InstallPlan`** in OLM terms) strategy plays a role whi #### Using Installation Script 1. Clone and checkout the required csm-operator version using ```bash -git clone -b v1.4.0 https://github.com/dell/csm-operator.git +git clone -b v1.4.1 https://github.com/dell/csm-operator.git ``` 2. `cd csm-operator` 3. Execute `bash scripts/install.sh --upgrade` . This command will install the latest version of the operator. @@ -376,7 +376,7 @@ The following notes explain some of the general items to take care of. 1. If you are trying to upgrade the CSI driver from an older version, make sure to modify the _configVersion_ field. ```yaml driver: - configVersion: v2.9.0 + configVersion: v2.9.1 ``` ## Custom Resource Definitions diff --git a/content/docs/deployment/csmoperator/drivers/_index.md b/content/docs/deployment/csmoperator/drivers/_index.md index 9dadf6f858..f13d779234 100644 --- a/content/docs/deployment/csmoperator/drivers/_index.md +++ b/content/docs/deployment/csmoperator/drivers/_index.md @@ -58,7 +58,7 @@ The CSI Drivers and CSM Modules installed by the Dell CSM Operator can be update 1. If you are trying to upgrade the CSI driver from an older version, make sure to modify the _configVersion_ field if required. ```yaml driver: - configVersion: v2.9.0 + configVersion: v2.9.1 ``` 2. Do not try to update the operator by modifying the original `CustomResource` manifest file and running the `kubectl apply -f` command. As part of the driver installation, the Operator sets some annotations on the `CustomResource` object which are further utilized in some workflows (like detecting upgrade of drivers). If you run the `kubectl apply -f` command to update the driver, these annotations are overwritten and this may lead to failures. diff --git a/content/docs/deployment/csmoperator/release/_index.md b/content/docs/deployment/csmoperator/release/_index.md index 528dbdccbc..bccec7568b 100644 --- a/content/docs/deployment/csmoperator/release/_index.md +++ b/content/docs/deployment/csmoperator/release/_index.md @@ -6,7 +6,7 @@ Description: > Release notes for Dell Container Storage Modules Operator --- -## Release Notes - Container Storage Modules Operator v1.4.0 +## Release Notes - Container Storage Modules Operator v1.4.1 @@ -29,6 +29,44 @@ Description: > - [#988 - [BUG]: CSM Operator fails to install CSM Replication on the remote cluster](https://github.com/dell/csm/issues/988) - [#989 - [BUG]: Allow volume prefix to be set via CSM operator](https://github.com/dell/csm/issues/989) - [#990 - [BUG]: X_CSI_AUTH_TYPE cannot be set in CSM Operator](https://github.com/dell/csm/issues/990) +- [#1110 - [BUG]: Multi Controller defect - sidecars timeout](https://github.com/dell/csm/issues/1110) +- [#1117 - [BUG]: Operator crashes when deployed from OpenShift with OLM](https://github.com/dell/csm/issues/1117) +- [#1120 - [BUG]: Skip Certificate Validation is not propagated to Authorization module in CSM Operator](https://github.com/dell/csm/issues/1120) +- [#1122 - [BUG]: CSM Operator does not calculate status correctly when module is deployed with driver](https://github.com/dell/csm/issues/1122) ### Known Issues -There are no known issues in this release. \ No newline at end of file +| Issue | Workaround | +|-------|------------| +| The images of sideCars are currently missing in the sample YAMLs in the offline bundle. As a consequence, the csm-operator is pulling them from registry.k8s.io. | We recommend manually updating the images of sideCars in the sample YAML file, for example, `storage_csm_powerflex_v291.yaml`, before proceeding with the driver installation. Here is an example snippet for the sideCars section in the YAML file: + + ```yaml + sideCars: + # 'k8s' represents a string prepended to each volume created by the CSI driver + - name: provisioner + image: /csi-provisioner:v3.6.2 + args: ["--volume-name-prefix=k8s"] + - name: attacher + image: /csi-attacher:v4.4.2 + - name: registrar + image: /csi-node-driver-registrar:v2.9.1 + - name: resizer + image: /csi-resizer:v1.9.2 + - name: snapshotter + image: /csi-snapshotter:v6.3.2 + + # sdc-monitor is disabled by default, due to high CPU usage + - name: sdc-monitor + enabled: false + image: /sdc:4.5 + envs: + - name: HOST_PID + value: "1" + - name: MDM + value: "10.xx.xx.xx,10.xx.xx.xx" # Do not add mdm value here if it is present in secret + + # health monitor is disabled by default, refer to driver documentation before enabling it + # Also set the env variable controller.envs.X_CSI_HEALTH_MONITOR_ENABLED to "true". + - name: csi-external-health-monitor-controller + enabled: false + image: /csi-external-health-monitor-controller:v0.10.0 + args: ["--monitor-interval=60s"] diff --git a/content/docs/replication/deployment/install-repctl.md b/content/docs/replication/deployment/install-repctl.md index 03268a4d68..9715a917a4 100644 --- a/content/docs/replication/deployment/install-repctl.md +++ b/content/docs/replication/deployment/install-repctl.md @@ -13,14 +13,14 @@ Before you begin, make sure you have the repctl tool available. You can download a pre-built repctl binary from our [Releases](https://github.com/dell/csm-replication/releases) page. ```shell -wget https://github.com/dell/csm-replication/releases/download/v1.7.0/repctl-linux-amd64 +wget https://github.com/dell/csm-replication/releases/download/v1.7.1/repctl-linux-amd64 mv repctl-linux-amd64 repctl chmod +x repctl ``` Alternately, if you want to build the binary yourself, you can follow these steps: ```shell -git clone -b v1.7.0 https://github.com/dell/csm-replication.git +git clone -b v1.7.1 https://github.com/dell/csm-replication.git cd csm-replication/repctl make build ``` diff --git a/content/docs/replication/deployment/install-script.md b/content/docs/replication/deployment/install-script.md index 0457809d0a..a01226fd5d 100644 --- a/content/docs/replication/deployment/install-script.md +++ b/content/docs/replication/deployment/install-script.md @@ -9,11 +9,11 @@ description: Installation of CSM for Replication using script (Helm chart) > **_NOTE:_** These steps should be repeated on all Kubernetes clusters where you want to configure replication. ```shell -git clone -b v1.7.0 https://github.com/dell/csm-replication.git +git clone -b v1.7.1 https://github.com/dell/csm-replication.git cd csm-replication kubectl create ns dell-replication-controller # Download and modify the default values.yaml file if you wish to customize your deployment in any way -wget -O myvalues.yaml https://raw.githubusercontent.com/dell/helm-charts/csm-replication-1.7.0/charts/csm-replication/values.yaml +wget -O myvalues.yaml https://raw.githubusercontent.com/dell/helm-charts/csm-replication-1.7.1/charts/csm-replication/values.yaml bash scripts/install.sh --values ./myvalues.yaml ``` >Note: Current installation method allows you to specify custom `:` entries to be appended to controller's `/etc/hosts` file. It can be useful if controller is being deployed in private environment where DNS is not set up properly, but kubernetes clusters use FQDN as API server's address. diff --git a/content/docs/replication/release/_index.md b/content/docs/replication/release/_index.md index f8cd95ab88..bbfe6dafad 100644 --- a/content/docs/replication/release/_index.md +++ b/content/docs/replication/release/_index.md @@ -6,7 +6,7 @@ Description: > Dell Container Storage Modules (CSM) release notes for replication --- -## Release Notes - CSM Replication 1.7.0 +## Release Notes - CSM Replication 1.7.1 diff --git a/content/docs/replication/upgrade.md b/content/docs/replication/upgrade.md index 16620b906d..4e3d496a34 100644 --- a/content/docs/replication/upgrade.md +++ b/content/docs/replication/upgrade.md @@ -45,7 +45,7 @@ On PowerScale systems, an additional step is needed when upgrading to CSM Replic Make sure the appropriate release branch is available on the machine performing the upgrade by running: ```bash -git clone -b v1.7.0 https://github.com/dell/csm-replication.git +git clone -b v1.7.1 https://github.com/dell/csm-replication.git ``` ### Upgrading with Helm diff --git a/content/docs/resiliency/release/_index.md b/content/docs/resiliency/release/_index.md index 91a9217111..f85176810c 100644 --- a/content/docs/resiliency/release/_index.md +++ b/content/docs/resiliency/release/_index.md @@ -6,7 +6,7 @@ Description: > Dell Container Storage Modules (CSM) release notes for resiliency --- -## Release Notes - CSM Resiliency 1.7.0 +## Release Notes - CSM Resiliency 1.8.1