OSDOCS-1720 bug fixes for 4-6 branch only

[bobfuru]

Follow up to #28034 and to this comment that brings OCP 4.6 docs up to date for:

• CSI snapshot controller namespace, as reported in https://bugzilla.redhat.com/show_bug.cgi?id=1906288
• Use of snapshot apiVersion snapshot.storage.k8s.io/v1beta1
• Adding modules/persistent-storage-csi-drivers-supported.adoc using the drivers supported up to OCP 4.6

[openshift-docs-preview-bot]

The preview will be available shortly at:

• modules/persistent-storage-csi-snapshots-operator.adoc: https://OSDOCS-1720-bugs-4-6--ocpdocs.netlify.com/openshift-enterprise/latest/modules/persistent-storage-csi-snapshots-operator.html

[bobfuru]

@duanwei33 PTAL for QE

[duanwei33]

@bobfuru
Is there another bz to track PersistentVolume and PersistentVolumeClaim as not a CRD?

Similar to the PersistentVolume CRD, the VolumeSnapshotContent CRD is a cluster resource that points to a real snapshot in the storage back end.
Similar to the PersistentVolumeClaim CRD, the VolumeSnapshot CRD defines a developer request for a snapshot.

[bobfuru]

@duanwei33 - Removed Cinder, let me know if this looks good now, thanks!

[bobfuru]

@bobfuru
Is there another bz to track PersistentVolume and PersistentVolumeClaim as not a CRD?

Similar to the PersistentVolume CRD, the VolumeSnapshotContent CRD is a cluster resource that points to a real snapshot in the storage back end.
Similar to the PersistentVolumeClaim CRD, the VolumeSnapshot CRD defines a developer request for a snapshot.

Good catch on this. I've updated this PR and the 4.5 PR (#28330) to conditionally reflect the additional bug fixes that were also introduced in 4.7 (#28034).

[duanwei33]

/lgtm

[openshift-ci-robot]

New changes are detected. LGTM label has been removed.

[bobfuru]

@openshift/team-documentation PTAL

[sfortner-RH]

lgtm!

[sfortner-RH]

Do we need to spell out the first instance of CSI here for clarity. There doesn't seem to be a consolidated viewpoint on doing this in OCP, but if a user reaches this doc from Google will they know what that acronym stands for? I always spell out the first instance of an acronym in all of my topics, even if they are nested together in the same assembly, and then proceed with acronym throughout for this reason. But it's also a hard ingrained habit from past roles too. It's fine as it, just some thoughts :)

[bobfuru]

Yes, I'm in total agreement. I try to spell out on first instance at the module level but missed this one, now fixed. Thanks!