Skip to content

Commit

Permalink
Add dell/csm#1205 to known issues (#1045)
Browse files Browse the repository at this point in the history
* Add #1205 to known issues

* Fix yaml snippet displaying issue
  • Loading branch information
AkshaySainiDell authored Mar 29, 2024
1 parent cb8ffac commit 63f48db
Show file tree
Hide file tree
Showing 8 changed files with 21 additions and 11 deletions.
8 changes: 3 additions & 5 deletions content/docs/authorization/release/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,6 @@ Description: >






### New Features/Changes

- [#926 - [FEATURE]: Fixing the linting, formatting and vetting issues](https://github.com/dell/csm/issues/926)
Expand All @@ -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|
1 change: 1 addition & 0 deletions content/docs/deployment/csmoperator/release/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 <secret-namespace> <secret-name>`|
| 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|
5 changes: 3 additions & 2 deletions content/v1/authorization/release/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -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|
1 change: 1 addition & 0 deletions content/v1/deployment/csmoperator/release/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 <secret-namespace> <secret-name>`|
| 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
Expand Down
5 changes: 3 additions & 2 deletions content/v2/authorization/release/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -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|
4 changes: 3 additions & 1 deletion content/v2/deployment/csmoperator/release/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
| 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|
4 changes: 4 additions & 0 deletions content/v3/authorization/release/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -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|
4 changes: 3 additions & 1 deletion content/v3/deployment/csmoperator/release/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
| 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|

0 comments on commit 63f48db

Please sign in to comment.