Merge branch 'main' into cert-csi_version-fix

content/docs/deployment/csmoperator/drivers/powermax.md

@@ -71,7 +71,7 @@ Use a tool such as `openssl` to generate this secret using the example below:
 ```bash
 openssl genrsa -out tls.key 2048
 openssl req -new -key tls.key -out tls.csr -config openssl.cnf
-openssl x509 -req -in tls.csr -signkey tls.key -out tls.crt -days 3650 -extensions v3_req -extfile openssl.cnf
+openssl x509 -req -in tls.csr -signkey tls.key -out tls.crt -days 3650 -extensions req_ext -extfile openssl.cnf
 kubectl create secret -n <namespace> tls csirevproxy-tls-secret --cert=tls.crt --key=tls.key
 ```
 

content/docs/deployment/helm/drivers/installation/powermax.md

@@ -70,7 +70,7 @@ Generate the CSR and Self-Signed Certificate:
 ```bash
 openssl genrsa -out tls.key 2048
 openssl req -new -key tls.key -out tls.csr -config openssl.cnf
-openssl x509 -req -in tls.csr -signkey tls.key -out tls.crt -days 3650 -extensions v3_req -extfile openssl.cnf
+openssl x509 -req -in tls.csr -signkey tls.key -out tls.crt -days 3650 -extensions req_ext -extfile openssl.cnf
 ```
 
 ### Install Helm 3

content/v1/_index.md

@@ -1,12 +1,17 @@
 
 ---
-title: "Documentation"
-linkTitle: "Documentation"
+title: "Container Storage Modules"
+linkTitle: "Container Storage Modules"
+weight: 20
+no_list: true
 ---
 
-{{% pageinfo color="primary" %}}
+{{% pageinfo color="dark" %}}
+<span><span/>{{< message text="6" >}}
+{{% /pageinfo %}}
 
-1. <span><span/>{{< message text="6" >}}
+{{% pageinfo color="primary" %}}
+1. <span><span/>{{< message text="8" >}}
 
 2. <span><span/>{{< message text="7" >}}
 

content/v1/applicationmobility/_index.md

@@ -6,8 +6,8 @@ Description: >
   Application Mobility
 ---
 
-{{% pageinfo color="primary" %}}
-We are pleased to announce that Application Mobility will be available with Container Storage Modules starting early next year (2025).
+{{% pageinfo color="primary" %}} 
+{{< message text="10" >}} 
 {{% /pageinfo %}}
 
 Container Storage Modules for Application Mobility provide Kubernetes administrators the ability to clone their stateful application workloads and application data to other clusters, either on-premise or in the cloud.

content/v1/applicationmobility/release/_index.md

@@ -5,17 +5,15 @@ weight: 5
 Description: >
   Release Notes
 ---
-{{% pageinfo color="primary" %}}
-We are pleased to announce that Application Mobility will be available with Container Storage Modules starting early next year (2025).
+{{% pageinfo color="primary" %}} 
+{{< message text="10" >}} 
 {{% /pageinfo %}}
 
-## Release Notes - CSM Application Mobility v1.2.0
+## Release Notes - CSM Application Mobility v1.3.0
 
 
 ### New Features/Changes
 
-- [#1472 - [FEATURE]: Support for Kubernetes 1.31](https://github.com/dell/csm/issues/1472)
-
 ### Fixed Issues
 
 ### Known Issues

content/v1/authorization/_index.md

@@ -16,4 +16,4 @@ Kubernetes administrators will have an interface to create, delete, and manage r
 
 Currently, we have two versions of Authorization, **v1.x** and **v2.x**. **v2.x is not backward compatible with v1.x versions**.
 
-**Deprecation Notice Pre-Wire: Starting with CSM 1.13, Authorization v1.x will be deprecated and will be officially discontinued by CSM 1.15 in September 2025. Please migrate to Authorization v2.0 before then to avoid any issues using the v2 Migration guide linked below.**
+**Starting with CSM 1.13, Authorization v1.x will be deprecated and will be officially discontinued by CSM 1.15 in September 2025. Please migrate to Authorization v2.0 before then to avoid any issues using the v2 Migration guide linked below.**

content/v1/authorization/v1.x/configuration/powerflex/_index.md

@@ -10,7 +10,7 @@ description: >
 Given a setup where Kubernetes, a storage system, and the CSM for Authorization Proxy Server are deployed, follow these steps to configure the CSI Drivers to work with the Authorization sidecar:
 
 1. Apply the secret containing the tenant token data into the driver namespace. It's assumed that the Kubernetes administrator has the token secret manifest, generated by your storage administrator via [Generate a Token](../proxy-server/#generate-a-token), saved in `/tmp/token.yaml`.
-   
+
    #It is assumed that array type powerflex has the namepace "vxflexos".
    ```console
     kubectl apply -f /tmp/token.yaml -n vxflexos
@@ -75,7 +75,6 @@ Given a setup where Kubernetes, a storage system, and the CSM for Authorization
       mdm: "10.0.0.3,10.0.0.4"
     ```
 
-
     **Operator**
 
     Refer to the [Create Secret](../../../../deployment/csmoperator/drivers/powerflex/#create-secret) section to prepare `secret.yaml` to configure the driver to communicate with the CSM Authorization sidecar.
@@ -105,11 +104,11 @@ Given a setup where Kubernetes, a storage system, and the CSM for Authorization
     Refer to the [Install the Driver](../../../../deployment/helm/drivers/installation/powerflex/#install-the-driver) section to edit the parameters in `myvalues.yaml` to enable CSM Authorization.
 
     - Update `authorization.enabled` to `true`.
-    
+
     - Update `images.authorization` to the image of the CSM Authorization sidecar. In most cases, you can leave the default value.
 
     - Update `authorization.proxyHost` to the hostname of the CSM Authorization Proxy Server. `csm-authorization.com` is a placeholder for the proxyHost. See the administrator of CSM for Authorization for the correct value.
-    
+
     - Update `authorization.skipCertificateValidation` to `true` or `false` depending on if you want to disable or enable certificate validation of the CSM Authorization Proxy Server.
 
     Example:
@@ -119,8 +118,8 @@ Given a setup where Kubernetes, a storage system, and the CSM for Authorization
       enabled: true
 
       # sidecarProxyImage: the container image used for the csm-authorization-sidecar.
-      # Default value: quay.io/dell/container-storage-modules/csm-authorization-sidecar:v1.12.0
-      sidecarProxyImage: quay.io/dell/container-storage-modules/csm-authorization-sidecar:v1.12.0
+      # Default value: quay.io/dell/container-storage-modules/csm-authorization-sidecar:v1.13.0
+      sidecarProxyImage: quay.io/dell/container-storage-modules/csm-authorization-sidecar:v1.13.0
 
       # proxyHost: hostname of the csm-authorization server
       # Default value: None
@@ -148,18 +147,18 @@ Given a setup where Kubernetes, a storage system, and the CSM for Authorization
 
     - Update the `SKIP_CERTIFICATE_VALIDATION` environment value to `true` or `false` depending on if you want to disable or enable certificate validation of the CSM Authorization Proxy Server.
 
-    Example: 
+    Example:
 
     ```yaml
     modules:
       # Authorization: enable csm-authorization for RBAC
       - name: authorization
         # enable: Enable/Disable csm-authorization
         enabled: true
-        configVersion: v1.12.0
+        configVersion: v1.13.0
         components:
         - name: karavi-authorization-proxy
-          image: quay.io/dell/container-storage-modules/csm-authorization-sidecar:v1.12.0
+          image: quay.io/dell/container-storage-modules/csm-authorization-sidecar:v1.13.0
           envs:
             # proxyHost: hostname of the csm-authorization server
             - name: "PROXY_HOST"

content/v1/authorization/v1.x/configuration/powermax/_index.md

@@ -28,7 +28,6 @@ Given a setup where Kubernetes, a storage system, and the CSM for Authorization
    | skipCertificateValidation  | A boolean that enables/disables certificate validation of the backend storage array. This parameter is not used. | No | true |
    | isDefault | A boolean that indicates if the array is the default array. This parameter is not used. | No | default value from values.yaml |
 
-
 Create the karavi-authorization-config secret using this command:
   ```bash
 
@@ -72,11 +71,11 @@ Create the karavi-authorization-config secret using this command:
     - Update `global.managementServers.endpoint` to match the localhost endpoint in `samples/secret/karavi-authorization-config.json`.
 
     - Update `authorization.enabled` to `true`.
-    
+
     - Update `images.authorization` to the image of the CSM Authorization sidecar. In most cases, you can leave the default value.
 
     - Update `authorization.proxyHost` to the hostname of the CSM Authorization Proxy Server. `csm-authorization.com` is a placeholder for the proxyHost. See the administrator of CSM for Authorization for the correct value.
-    
+
     - Update `authorization.skipCertificateValidation` to `true` or `false` depending on if you want to disable or enable certificate validation of the CSM Authorization Proxy Server.
 
     - Update `csireverseproxy.deployAsSidecar` to `true`.
@@ -103,8 +102,8 @@ Create the karavi-authorization-config secret using this command:
       enabled: true
 
       # sidecarProxyImage: the container image used for the csm-authorization-sidecar.
-      # Default value: quay.io/dell/container-storage-modules/csm-authorization-sidecar:v1.12.0
-      sidecarProxyImage: quay.io/dell/container-storage-modules/csm-authorization-sidecar:v1.12.0
+      # Default value: quay.io/dell/container-storage-modules/csm-authorization-sidecar:v1.13.0
+      sidecarProxyImage: quay.io/dell/container-storage-modules/csm-authorization-sidecar:v1.13.0
 
       # proxyHost: hostname of the csm-authorization server
       # Default value: None
@@ -134,15 +133,15 @@ Create the karavi-authorization-config secret using this command:
 
     - Update the `DeployAsSidecar` environment variable for the `csipowermax-reverseproxy` component to `true`.
 
-    Example: 
+    Example:
 
     ```yaml
     modules:
       - name: csireverseproxy
         # enabled: Always set to true
         enabled: true
         forceRemoveModule: true
-        configVersion: v2.11.0
+        configVersion: v2.12.0
         components:
           - name: csipowermax-reverseproxy
             envs:
@@ -152,10 +151,10 @@ Create the karavi-authorization-config secret using this command:
       - name: authorization
         # enable: Enable/Disable csm-authorization
         enabled: true
-        configVersion: v1.12.0
+        configVersion: v1.13.0
         components:
         - name: karavi-authorization-proxy
-          image: quay.io/dell/container-storage-modules/csm-authorization-sidecar:v1.12.0
+          image: quay.io/dell/container-storage-modules/csm-authorization-sidecar:v1.13.0
           envs:
             # proxyHost: hostname of the csm-authorization server
             - name: "PROXY_HOST"

content/v1/authorization/v1.x/configuration/powerscale/_index.md

@@ -10,7 +10,7 @@ description: >
 Given a setup where Kubernetes, a storage system, and the CSM for Authorization Proxy Server are deployed, follow these steps to configure the CSI Drivers to work with the Authorization sidecar:
 
 1. Apply the secret containing the token data into the driver namespace. It's assumed that the Kubernetes administrator has the token secret manifest, generated by your storage administrator via [Generate a Token](../proxy-server/#generate-a-token), saved in `/tmp/token.yaml`.
-    
+
     #It is assumed that array type powerscale has the namespace "isilon".
     ```console
     kubectl apply -f /tmp/token.yaml -n isilon
@@ -28,7 +28,6 @@ Given a setup where Kubernetes, a storage system, and the CSM for Authorization
    | skipCertificateValidation  | A boolean that enables/disables certificate validation of the backend storage array. This parameter is not used. | No | true |
    | isDefault | A boolean that indicates if the array is the default array. This parameter is not used. | No | default value from values.yaml |
 
-
 Create the karavi-authorization-config secret using this command:
 
 ```bash
@@ -107,17 +106,17 @@ kubectl -n isilon create secret generic karavi-authorization-config --from-file=
     ```
 
 5. Enable CSM Authorization in the driver installation applicable to your installation method.
-    
+
     **Helm**
 
     Refer to the [Install the Driver](../../../../deployment/helm/drivers/installation/isilon/#install-the-driver) section to edit the parameters in `my-isilon-settings.yaml` file to enable CSM Authorization.
 
     - Update `authorization.enabled` to `true`.
-    
+
     - Update `images.authorization` to the image of the CSM Authorization sidecar. In most cases, you can leave the default value.
 
     - Update `authorization.proxyHost` to the hostname of the CSM Authorization Proxy Server. `csm-authorization.com` is a placeholder for the proxyHost. See the administrator of CSM for Authorization for the correct value.
-    
+
     - Update `authorization.skipCertificateValidation` to `true` or `false` depending on if you want to disable or enable certificate validation of the CSM Authorization Proxy Server.
 
    Example:
@@ -127,8 +126,8 @@ kubectl -n isilon create secret generic karavi-authorization-config --from-file=
       enabled: true
 
       # sidecarProxyImage: the container image used for the csm-authorization-sidecar.
-      # Default value: quay.io/dell/container-storage-modules/csm-authorization-sidecar:v1.12.0
-      sidecarProxyImage: quay.io/dell/container-storage-modules/csm-authorization-sidecar:v1.12.0
+      # Default value: quay.io/dell/container-storage-modules/csm-authorization-sidecar:v1.13.0
+      sidecarProxyImage: quay.io/dell/container-storage-modules/csm-authorization-sidecar:v1.13.0
 
       # proxyHost: hostname of the csm-authorization server
       # Default value: None
@@ -162,10 +161,10 @@ kubectl -n isilon create secret generic karavi-authorization-config --from-file=
       - name: authorization
         # enable: Enable/Disable csm-authorization
         enabled: true
-        configVersion: v1.12.0
+        configVersion: v1.13.0
         components:
         - name: karavi-authorization-proxy
-          image: quay.io/dell/container-storage-modules/csm-authorization-sidecar:v1.12.0
+          image: quay.io/dell/container-storage-modules/csm-authorization-sidecar:v1.13.0
           envs:
             # proxyHost: hostname of the csm-authorization server
             - name: "PROXY_HOST"

content/v1/authorization/v1.x/release/_index.md

@@ -6,14 +6,20 @@ Description: >
   Dell Container Storage Modules (CSM) release notes for authorization
 ---
 
-## Release Notes - CSM Authorization 1.12.0
+## Release Notes - CSM Authorization 1.13.0
 
 {{% pageinfo color="primary" %}}
 {{< message text="5" >}}
 {{% /pageinfo %}}
 
 ### New Features/Changes
 
+- [#1560 - [FEATURE]: CSM support for OpenShift 4.18](https://github.com/dell/csm/issues/1560)
+- [#1561 - [FEATURE]: Added support for Kubernetes 1.32 ](https://github.com/dell/csm/issues/1561)
+- [#1563 - [FEATURE]: Support KubeVirt for CSM modules](https://github.com/dell/csm/issues/1563)
+- [#1610 - [FEATURE]: Added support for PowerStore 4.1 ](https://github.com/dell/csm/issues/1610)
+- [#1611 - [FEATURE]: Added support for PowerScale 9.10](https://github.com/dell/csm/issues/1611)
+
 ### Fixed Issues
 
 ### Known Issues

content/v1/authorization/v2.x/configuration/powerflex/_index.md

@@ -117,7 +117,7 @@ Given a setup where Kubernetes, a storage system, and the CSM for Authorization
 
     - Update the `SKIP_CERTIFICATE_VALIDATION` environment value to `true` or `false` depending on if you want to disable or enable certificate validation of the CSM Authorization Proxy Server.
 
-    - Do not update the `configVersion`. You will notice in the example that it is set to v1.12.0, this ensures that Operator checks on version support do not prevent deployment of the v2.0.0 version of authorization.
+    - Do not update the `configVersion`. You will notice in the example that it is set to v1.13.0, this ensures that Operator checks on version support do not prevent deployment of the v2.0.0 version of authorization.
 
     Example:
 
@@ -127,7 +127,7 @@ Given a setup where Kubernetes, a storage system, and the CSM for Authorization
       - name: authorization
         # enable: Enable/Disable csm-authorization
         enabled: true
-        configVersion: v1.12.0
+        configVersion: v1.13.0
         components:
         - name: karavi-authorization-proxy
           image: quay.io/dell/container-storage-modules/csm-authorization-sidecar:v2.0.0
@@ -175,4 +175,4 @@ Given a setup where Kubernetes, a storage system, and the CSM for Authorization
       skipCertificateValidation: true
     ```
 
-1. Install the Dell CSI PowerFlex driver following the appropriate documenation for your installation method.
+1. Install the Dell CSI PowerFlex driver following the appropriate documentation for your installation method.

content/v1/authorization/v2.x/configuration/powermax/_index.md

@@ -7,6 +7,7 @@ description: >
 {{% pageinfo color="primary" %}}
 {{< message text="1" >}}
 {{% /pageinfo %}}
+
 ## Configuring PowerMax CSI Driver with CSM for Authorization
 
 Given a setup where Kubernetes, a storage system, and the CSM for Authorization Proxy Server are deployed, follow these steps to configure the CSI Drivers to work with the Authorization sidecar:
@@ -71,11 +72,10 @@ Given a setup where Kubernetes, a storage system, and the CSM for Authorization
 5. **Operator Only**: Prepare the reverse proxy configmap using sample [here](https://github.com/dell/csm-operator/blob/main/samples/csireverseproxy/config.yaml). Fill in the appropriate values for driver configuration.
    Example: config.yaml
    ```yaml
-    mode: StandAlone # Mode for the reverseproxy, should not be changed
     port: 2222
     logLevel: debug
     logFormat: text
-    standAloneConfig:
+    config:
     storageArrays:
         - storageArrayId: "000000000001" # arrayID
         primaryURL: "https://localhost:9400" # primary unisphere for arrayID
@@ -105,7 +105,7 @@ Given a setup where Kubernetes, a storage system, and the CSM for Authorization
 
     - Update the `SKIP_CERTIFICATE_VALIDATION` environment value to `true` or `false` depending on if you want to disable or enable certificate validation of the CSM Authorization Proxy Server.
 
-    - Do not update the `configVersion`. You will notice in the example that it is set to v1.12.0, this ensures that Operator checks on version support do not prevent deployment of the v2.0.0-alpha authorization tech preview.
+    - Do not update the `configVersion`. You will notice in the example that it is set to v1.13.0, this ensures that Operator checks on version support do not prevent deployment of the v2.0.0-alpha authorization tech preview.
 
     Example:
 
@@ -116,12 +116,12 @@ Given a setup where Kubernetes, a storage system, and the CSM for Authorization
         # enabled: Always set to true
         enabled: true
         forceRemoveModule: true
-        configVersion: v2.11.0
+        configVersion: v2.12.0
         components:
         - name: csipowermax-reverseproxy
         # image: Define the container images used for the reverse proxy
         # Default value: None
-          image: quay.io/dell/container-storage-modules/csipowermax-reverseproxy:v2.11.0
+          image: quay.io/dell/container-storage-modules/csipowermax-reverseproxy:v2.12.0
           envs:
           # "tlsSecret" defines the TLS secret that is created with certificate
           # and its associated key
@@ -143,7 +143,7 @@ Given a setup where Kubernetes, a storage system, and the CSM for Authorization
       - name: authorization
         # enable: Enable/Disable csm-authorization
         enabled: true
-        configVersion: v1.12.0
+        configVersion: v1.13.0
         components:
         - name: karavi-authorization-proxy
           image: quay.io/dell/container-storage-modules/csm-authorization-sidecar:v2.0.0