diff --git a/content/docs/authorization/release/_index.md b/content/docs/authorization/release/_index.md index a642a295af..164ec529b7 100644 --- a/content/docs/authorization/release/_index.md +++ b/content/docs/authorization/release/_index.md @@ -15,9 +15,6 @@ Description: > - - - ### New Features/Changes - [#926 - [FEATURE]: Fixing the linting, formatting and vetting issues](https://github.com/dell/csm/issues/926) @@ -26,5 +23,6 @@ Description: > ### Known Issues - -There are no known issues in this release. +| Issue | Workaround | +|-------|------------| +| CSM Operator does not support dynamic namespaces for Authorization. Despite successful installation in a namespace other than "authorization", errors may arise during volume creation. | Use the default namespace "authorization" for installing Authorization using CSM Operator| diff --git a/content/docs/csidriver/release/powerflex.md b/content/docs/csidriver/release/powerflex.md index 5b06d59117..4c58a16f56 100644 --- a/content/docs/csidriver/release/powerflex.md +++ b/content/docs/csidriver/release/powerflex.md @@ -38,6 +38,7 @@ A CSI ephemeral pod may not get created in OpenShift 4.13 and fail with the erro | 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. | | Resource quotas may not work properly with the CSI PowerFlex driver. PowerFlex is only able to assign storage in 8Gi chunks, so if a create volume call is made with a size not divisible by 8Gi, CSI-PowerFlex will round up to the next 8Gi boundary when it provisions storage -- however, the resource quota will not record this size but rather the original size in the create request. This means that, for example, if a 10Gi resource quota is set, and a user provisions 10 1Gi PVCs, 80Gi of storage will actually be allocated, which is well over the amount specified in the resource quota. | For now, users should only provision volumes in 8Gi-divisible chunks if they want to use resource quotas. | +| Helm install of CSM for PowerFlex v1.10.0 is failing due to a duplicate `mountPath: /host_opt_emc_path` being added to volumeMounts charts/csi-vxflexos/templates/node.yaml. Error message is `Error: INSTALLATION FAILED: 1 error occurred: DaemonSet.apps "vxflexos-node" is invalid: spec.template.spec.initContainers[0].volumeMounts[4].mountPath: Invalid value: "/host_opt_emc_path": must be unique` | The issue can be resolved by removing the duplicate entry in [https://github.com/dell/helm-charts/blob/main/charts/csi-vxflexos/templates/node.yaml](https://github.com/dell/helm-charts/blob/main/charts/csi-vxflexos/templates/node.yaml) | ### Note: diff --git a/content/docs/deployment/csmoperator/release/_index.md b/content/docs/deployment/csmoperator/release/_index.md index 5803fd15c0..4aa71013b2 100644 --- a/content/docs/deployment/csmoperator/release/_index.md +++ b/content/docs/deployment/csmoperator/release/_index.md @@ -31,3 +31,4 @@ Description: > | Issue | Workaround | |-------|------------| | When CSM Operator creates a deployment that includes secrets (e.g., application-mobility, observability, cert-manager, velero), these secrets are not deleted on uninstall and will be left behind. For example, the `karavi-topology-tls`, `otel-collector-tls`, and `cert-manager-webhook-ca` secrets will not be deleted. | This should not cause any issues on the system, but all secrets present on the cluster can be found with `kubectl get secrets -A`, and any unwanted secrets can be deleted with `kubectl delete secret -n `| +| CSM Operator does not support dynamic namespaces for Authorization. Despite successful installation in a namespace other than "authorization", errors may arise during volume creation. | Use the default namespace "authorization" for installing Authorization using CSM Operator| diff --git a/content/docs/prerequisites/_index.md b/content/docs/prerequisites/_index.md index 45f270a75b..a82f4c3dac 100644 --- a/content/docs/prerequisites/_index.md +++ b/content/docs/prerequisites/_index.md @@ -10,7 +10,7 @@ weight: 1 {{}} | Platform | Version | OS Dependencies | |---------------|:----------------:|:------------------------:| -| PowerMax | PowerMax 2500/8500 PowerMaxOS 10 (6079)
PowerMaxOS 10.0.1 (6079)
PowerMaxOS 10.1 (6079)
PowerMax 2000/8000 - 5978.711.xxx
5978.479.xxx
Unisphere 10.0,10.0.1,10.1 | iscsi-initiator-utils
multipathd or powerpath
nvme-cli
nfs-utils | +| PowerMax | PowerMax 2500/8500 PowerMaxOS 10 (6079)
PowerMaxOS 10.0.1 (6079)
PowerMaxOS 10.1 (6079)
PowerMax 2000/8000 - 5978.711.711, 5978.714.714
5978.479.479
Unisphere 10.0,10.0.1,10.1 | iscsi-initiator-utils
multipathd or powerpath
nvme-cli
nfs-utils | | PowerFlex | 3.6.x, 4.0.x, 4.5.x | [SDC](https://www.dell.com/support/home/en-us/product-support/product/scaleio/drivers)| | Unity XT | 5.1.x, 5.2.x, 5.3.0 | iscsi-initiator-utils
multipathd
nfs-utils | | PowerScale | OneFS 9.3, 9.4, 9.5.0.x (x >= 5) | nfs-utils | diff --git a/content/v1/authorization/release/_index.md b/content/v1/authorization/release/_index.md index 3bcadd9408..07b4881533 100644 --- a/content/v1/authorization/release/_index.md +++ b/content/v1/authorization/release/_index.md @@ -27,5 +27,6 @@ Description: > ### Known Issues - -There are no known issues in this release. +| Issue | Workaround | +|-------|------------| +| CSM Operator does not support dynamic namespaces for Authorization. Despite successful installation in a namespace other than "authorization", errors may arise during volume creation. | Use the default namespace "authorization" for installing Authorization using CSM Operator| diff --git a/content/v1/deployment/csmoperator/release/_index.md b/content/v1/deployment/csmoperator/release/_index.md index a7c6b08e83..0efac132a7 100644 --- a/content/v1/deployment/csmoperator/release/_index.md +++ b/content/v1/deployment/csmoperator/release/_index.md @@ -46,6 +46,7 @@ Description: > |-------|------------| | The status field of a csm object as deployed by CSM Operator may, in limited cases, display an incorrect status for a deployment. | As a workaround, the health of the deployment can be determined by checking the health of the pods. | | When CSM Operator creates a deployment that includes secrets (e.g., application-mobility, observability, cert-manager, velero), these secrets are not deleted on uninstall and will be left behind. For example, the `karavi-topology-tls`, `otel-collector-tls`, and `cert-manager-webhook-ca` secrets will not be deleted. | This should not cause any issues on the system, but all secrets present on the cluster can be found with `kubectl get secrets -A`, and any unwanted secrets can be deleted with `kubectl delete secret -n `| +| CSM Operator does not support dynamic namespaces for Authorization. Despite successful installation in a namespace other than "authorization", errors may arise during volume creation. | Use the default namespace "authorization" for installing Authorization using CSM Operator| | 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 diff --git a/content/v2/authorization/release/_index.md b/content/v2/authorization/release/_index.md index a64bec93ca..c2b85c06e0 100644 --- a/content/v2/authorization/release/_index.md +++ b/content/v2/authorization/release/_index.md @@ -20,5 +20,6 @@ Description: > - [#916 - [BUG]: Remove references to deprecated io/ioutil package](https://github.com/dell/csm/issues/916) ### Known Issues - -There are no known issues in this release. +| Issue | Workaround | +|-------|------------| +| CSM Operator does not support dynamic namespaces for Authorization. Despite successful installation in a namespace other than "authorization", errors may arise during volume creation. | Use the default namespace "authorization" for installing Authorization using CSM Operator| diff --git a/content/v2/deployment/csmoperator/release/_index.md b/content/v2/deployment/csmoperator/release/_index.md index 5ac816b526..b5f331afa9 100644 --- a/content/v2/deployment/csmoperator/release/_index.md +++ b/content/v2/deployment/csmoperator/release/_index.md @@ -24,4 +24,6 @@ Description: > - [#898 - [BUG]: Unable to pull podmon image from local repository for offline install](https://github.com/dell/csm/issues/898) ### Known Issues -There are no known issues in this release. \ No newline at end of file +| Issue | Workaround | +|-------|------------| +| CSM Operator does not support dynamic namespaces for Authorization. Despite successful installation in a namespace other than "authorization", errors may arise during volume creation. | Use the default namespace "authorization" for installing Authorization using CSM Operator| \ No newline at end of file diff --git a/content/v3/authorization/release/_index.md b/content/v3/authorization/release/_index.md index 5383614d75..3390a862c4 100644 --- a/content/v3/authorization/release/_index.md +++ b/content/v3/authorization/release/_index.md @@ -21,3 +21,7 @@ Description: > - Authorization RPM installation should use nogpgcheck for k3s-selinux package. ([#772](https://github.com/dell/csm/issues/772)) - CSM Authorization - karavictl generate token should output valid yaml. ([#767](https://github.com/dell/csm/issues/767)) +### Known Issues +| Issue | Workaround | +|-------|------------| +| CSM Operator does not support dynamic namespaces for Authorization. Despite successful installation in a namespace other than "authorization", errors may arise during volume creation. | Use the default namespace "authorization" for installing Authorization using CSM Operator| \ No newline at end of file diff --git a/content/v3/deployment/csmoperator/release/_index.md b/content/v3/deployment/csmoperator/release/_index.md index 397664e60b..5278fedd50 100644 --- a/content/v3/deployment/csmoperator/release/_index.md +++ b/content/v3/deployment/csmoperator/release/_index.md @@ -27,4 +27,6 @@ CSM 1.7.1 is applicable to helm based installations of PowerFlex driver. ### Known Issues -There are no known issues in this release. \ No newline at end of file +| Issue | Workaround | +|-------|------------| +| CSM Operator does not support dynamic namespaces for Authorization. Despite successful installation in a namespace other than "authorization", errors may arise during volume creation. | Use the default namespace "authorization" for installing Authorization using CSM Operator| \ No newline at end of file