Feature Overview (aka. Goal 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.

This feature lets your cluster expand storage volumes, even when access to those volumes requires a secret (for example: a credential for accessing a SAN fabric) to perform node expand operation.

Goals (aka. expected user outcomes)

• We get this upstream feature through Kubernetes rebase. 
• https://github.com/kubernetes/enhancements/issues/3107

csi.storage.k8s.io/node-expand-secret-name: test-secret
csi.storage.k8s.io/node-expand-secret-namespace: default

Requirements (aka. Acceptance Criteria):

We should ensure it works well in OCP and we have it documented in the release notes.

Documentation Considerations

No need to have proper documentation for this feature as it is not user facing. This can be useful for drivers & partners that require secret to expand volume and support that new feature. Partners should document its usage if needed.

We can limit documentation to release notes.

Interoperability Considerations

It's useful for drivers that actually support this feature.