Merge pull request #67893 from lpettyjo/OSDOCS-7671

OSDOCS#7671: Retroactive SC TP-> GA

Author: lpettyjo

modules/persistent-storage-csi-sc-multiple-none.adoc

@@ -16,35 +16,4 @@ There are two possible scenarios where PVCs can attempt to use a non-existent de
 
 * During installation, the installer creates a PVC requesting the default storage class, which has not yet been created.
 
-In the preceding scenarios, the PVCs remain in pending state indefinitely.
-
-{product-title} provides a feature to retroactively assign the default storage class to PVCs, so that they do not remain in the pending state. With this feature enabled, PVCs requesting the default storage class that are created when no default storage classes exists, remain in the pending state until a default storage class is created, or one of the existing storage classes is declared the default. As soon as the default storage class is created or declared, the PVC gets the new default storage class.
-
-:FeatureName: Retroactive default storage class assignment
-include::snippets/technology-preview.adoc[leveloffset=+1]
-
-=== Procedure
-
-To enable retroactive default storage class assignment:
-
-. Enable feature gates (see _Nodes_ → _Working with clusters_ → _Enabling features using feature gates_).
-+
-[IMPORTANT]
-====
-After turning on Technology Preview features using feature gates, they cannot be turned off. As a result, cluster upgrades are prevented.
-====
-+
-The following configuration example enables retroactive default storage class assignment, and all other Technology Preview features:
-+
-[source, yaml]
-----
-apiVersion: config.openshift.io/v1
-kind: FeatureGate
-metadata:
-  name: cluster
-spec:
-  featureSet: TechPreviewNoUpgrade <1>
-...
-----
-<1> Enables retroactive default storage class assignment.
-
+In the preceding scenarios, PVCs remain in the pending state indefinitely. To resolve this situation, create a default storage class or declare one of the existing storage classes as the default. As soon as the default storage class is created or declared, the PVCs get the new default storage class. If possible, the PVCs eventually bind to statically or dynamically provisioned PVs as usual, and move out of the pending state.