In-tree volume plugins remove dynamic provisioning support

[carlory]

Enhancement Description

• One-line enhancement description (can be used as a release note): Remove dynamic provisioning support from the hostPath in-tree volume plugin.
• Kubernetes Enhancement Proposal:
• Discussion Link:
  • Should we deprecate and remove the in-tree volume plugin hostpath dynamic provisioning feature? kubernetes#123804
• Primary contact (assignee): @carlory
• Responsible SIGs: sig-storage
• Enhancement target (which target equals to which milestone): 1.31
  • Alpha release target (x.y): 1.31
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s): add KEP to remove dynamic provisioning from in-tree plugins #4548
  • Code (k/k) update PR(s): the --enable-hostpath-provisioner option is deprecated  kubernetes#123841
  • Docs (k/website) update PR(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[carlory]

/sig storage

[sreeram-venkitesh]

/stage alpha

[sreeram-venkitesh]

Hello @carlory 👋, v1.31 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024.

This enhancement is targeting for stage alpha for v1.31 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: v1.31. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
• KEP readme has up-to-date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline so that the PRR team has enough time to review your KEP before the enhancements freeze.

For this KEP, we need to do the following:

• Get add KEP to remove dynamic provisioning from in-tree plugins #4548 merged. For this you need to add a PRR approver in the PRR yaml file and also complete the PRR questionnaire (ideally before the PRR freeze deadline), as mentioned by @xing-yang here.

Please get the PRR review done and the KEP files merged before the enhancements freeze!

The status of this enhancement is marked as at risk for enhancement freeze.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Let me know if you have any questions! Thank you!

[MaryamTavakkoli]

Hello @carlory 👋, 1.31 Docs Shadow here.
Does this enhancement work planned for 1.31 require any new docs or modifications to existing docs?
If so, please follow the steps here to open a PR against the dev-1.31 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, June 27, 2024, 18:00 PDT.
Also, take a look at Documenting for a release to get yourself familiarised with the docs requirement for the release.
Thank you!

[sreeram-venkitesh]

@carlory Pinging as a reminder that we are approaching the enhancements freeze deadline, which is on this Friday, June 14th!

[jpbetz]

PRR reviewer here. I'd like to see this deprecation guarded by a feature gate. I've added some comments.

I'm also curious how much value we get out of this deprecation? Should we be investing in it or would it be better to just mark the feature as forever deprecated and leave it as-is? (cc @msau42 )

[carlory]

@jpbetz @sreeram-venkitesh I appreciate your reminder. I have to postpone it to 1.32 because of a personal issue. I will update the KEP according to the feedback when I have time.

[sreeram-venkitesh]

/milestone clear