Epic Goal*

All references to RetroactiveDefaultStorageClass should be removed from upstream because it was GA in Kubernetes 1.28. The feature gate was kept for one release but should be removed in 1.29.

 
Why is this important? (mandatory)

It is part of feature graduation process and cleans up the codebase.

 
Scenarios (mandatory) 

None - cleanup task only.

Dependencies (internal and external) (mandatory)

None.

Contributing Teams(and contacts) (mandatory) 

Our expectation is that teams would modify the list below to fit the epic. Some epics may not need all the default groups but what is included here should accurately reflect who will be involved in delivering the epic.

• Development - required
• Documentation - not required
• QE - not required
• PX - not required
• Others - not required

Acceptance Criteria (optional)

• CI tests pass

Drawbacks or Risk (optional)

If any bugs are found we should not remove the feature gate to leave users the option to opt-out from the feature.

Done - Checklist (mandatory)

The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.

• CI Testing -  Basic e2e automationTests are merged and completing successfully
• Documentation - Content development is complete.
• QE - Test scenarios are written and executed successfully.
• Technical Enablement - Slides are complete (if requested by PLM)
• Engineering Stories Merged
• All associated work items with the Epic are closed
• Epic status should be “Release Pending”