Expose StorageClass Params To End Users (Configurable storage dynamic provisioning)

[jsafrane]

Feature Description

• One-line feature description (can be used as a release note): Expose StorageClass Params To End Users (aka Provisioning configuration in PVC)
• Primary contact (assignee): @jsafrane
• Responsible SIGs: @kubernetes/sig-storage-feature-requests
• Design proposal link (community repo): Allow pvc.Selector and pvc.Class both to be set. community#247
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @msau42 @gnufied
• Approver (likely from SIG/area to which feature belongs): @saad-ali
• Feature target (which target equals to which milestone):
  • Alpha release target (1.8)
  • Beta release target (>=1.9)
  • Stable release target (>1.9)

[idvoretskyi]

@jsafrane I've updated the feature description to fit the new template. Please, fill the empty fields in the new template (their actual state was unclear).

[apsinha]

@jsafrane also please add a one line description as requested in the template.

[idvoretskyi]

@jsafrane @kubernetes/sig-storage-feature-requests yet another request - please, update the feature description per template.

[saad-ali]

This will not make it to 1.7, moving to 1.8

[jsafrane]

sig-storage has agreed that this feature is not a priority to us. I am going to close my proposals and remove milestone from this issue. We appreciate any volunteers to resume this effort! Anyone is welcome to update the proposal and implement the feature!

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close