Epic Goal

Support upstream feature "NodeExpansion secret (e2e test)"" in OCP as Beta, i.e. test it and have docs for it (unless it's Alpha upstream).

Summary: A CSI driver can configure NodeExpansion secret in their StorageClass and it will get it when expanding a volume. This feature is useful only to CSI driver vendors and not to end users.

Why is this important?

• We get this upstream feature through Kubernetes rebase. We should ensure it works well in OCP and we have docs for it.

Upstream links

• Enhancement issue: https://github.com/kubernetes/enhancements/issues/3107
• KEP: https://github.com/kubernetes/enhancements/pull/3173

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. External: the feature is currently scheduled for Beta in Kubernetes 1.27, i.e. OCP 4.14, but it may change before Kubernetes 1.27 GA.

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>