NO-JIRA: [release-4.22] Enable ReadWriteOncePod for Cinder CSI

[kchawlani19]

Analysis / Root cause:
The Create PersistentVolumeClaim form gates access modes with a static provisioner map in frontend/public/components/storage/shared.ts. On 4.22, cinder.csi.openstack.org lists only ReadWriteOnce, so ReadWriteOncePod is grayed out. YAML creation of RWOP PVCs already works. The in-tree kubernetes.io/cinder entry also listed ReadWriteOncePod twice.

Solution description:
Backport of #16870 plus regression tests:

• cinder.csi.openstack.org: add ReadWriteOncePod for Filesystem and Block
• kubernetes.io/cinder: remove duplicate ReadWriteOncePod entries
• unit tests for the provisioner access-mode helpers

Screenshots / screen recording:
N/A (access-mode dropdown option enablement)

Test setup:
OpenShift on OpenStack with a StorageClass whose provisioner is cinder.csi.openstack.org.

Test cases:

1. Storage → PersistentVolumeClaims → Create PersistentVolumeClaim
2. Select a Cinder CSI StorageClass
3. Access mode options include "Read write once pod (RWOP)" alongside "Single user (RWO)"
4. Create a PVC with RWOP / Filesystem and confirm it binds
5. Repeat with volume mode Block
6. Regression: Manila CSI access modes unchanged

Browser conformance:

• Chrome
• Firefox
• Safari (or Epiphany on Linux)

Additional info:
Related to #16866
Backport of #16870
Tests on main: #17105

Cinder CSI reports SINGLE_NODE_SINGLE_WRITER, which maps to ReadWriteOncePod.

Reviewers and assignees:
/assign spadgett

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci-robot]

@kchawlani19: This pull request explicitly references no jira issue.

Details

In response to this:

Analysis / Root cause:
The Create PersistentVolumeClaim form gates access modes with a static provisioner map in frontend/public/components/storage/shared.ts. On 4.22, cinder.csi.openstack.org lists only ReadWriteOnce, so ReadWriteOncePod is grayed out. YAML creation of RWOP PVCs already works. The in-tree kubernetes.io/cinder entry also listed ReadWriteOncePod twice.

Solution description:
Backport of #16870 plus regression tests:

• cinder.csi.openstack.org: add ReadWriteOncePod for Filesystem and Block
• kubernetes.io/cinder: remove duplicate ReadWriteOncePod entries
• unit tests for the provisioner access-mode helpers

Screenshots / screen recording:
N/A (access-mode dropdown option enablement)

Test setup:
OpenShift on OpenStack with a StorageClass whose provisioner is cinder.csi.openstack.org.

Test cases:

1. Storage → PersistentVolumeClaims → Create PersistentVolumeClaim
2. Select a Cinder CSI StorageClass
3. Access mode options include "Read write once pod (RWOP)" alongside "Single user (RWO)"
4. Create a PVC with RWOP / Filesystem and confirm it binds
5. Repeat with volume mode Block
6. Regression: Manila CSI access modes unchanged

Browser conformance:

• Chrome
• Firefox
• Safari (or Epiphany on Linux)

Additional info:
Related to #16866
Backport of #16870
Tests on main: #17105

Cinder CSI reports SINGLE_NODE_SINGLE_WRITER, which maps to ReadWriteOncePod.

Reviewers and assignees:
/assign spadgett

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kchawlani19
Once this PR has been reviewed and has the lgtm label, please ask for approval from spadgett. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• frontend/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@kchawlani19: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.