Epic Goal

• Promote [KEP-3333|https://github.com/kubernetes/enhancements/pull/3337 beta upstream
• Loosen ordering requirements between PVCs and default SC creation.

Why is this important?

• There are some cases where default storage classes are not assigned or more than one default is defined.
• Can cause issues during OCP installation when there is no default SC defined yet

Scenarios

1. The admin marks the current default SC1 as non-default.
   Another user creates PVC requesting a default SC, by leaving pvc.spec.storageClassName=nil. The default SC does not exist at this point, therefore the admission plugin leaves the PVC untouched with pvc.spec.storageClassName=nil.
   The admin marks SC2 as default.
   PV controller, when reconciling the PVC, updates pvc.spec.storageClassName=nil to the new SC2.
   PV controller uses the new SC2 when binding / provisioning the PVC.

1. The installer creates PVC for the image registry first, requesting the default storage class by leaving pvc.spec.storageClassName=nil.
   The installer creates a default SC.
   PV controller, when reconciling the PVC, updates pvc.spec.storageClassName=nil to the new default SC.
   PV controller uses the new default SC when binding / provisioning the PVC.

Acceptance Criteria

• end to end test upstream
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Open questions::

1. …