Runtime assisted mounting of Persistent Volumes

[ddebroy]

Enhancement Description

• One-line enhancement description (can be used as a release note): Runtime assisted mounting of Persistent Volumes
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/pull/2893
• Discussion Link: July 15th SIG-Storage meeting, July 20th SIG-Node meeting
• Primary contact (assignee): @ddebroy
• Responsible SIGs: SIG-Storage and SIG-Node
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.25
  • Beta release target (x.y):
  • Stable release target (x.y):
• [ ] Alpha
  • [x] KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/2893
  • [ ] Code (k/k) update PR(s):
  • [ ] Docs (k/website) update PR(s):

[ddebroy]

/sig storage /sig node

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[ddebroy]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[ddebroy]

/remove-lifecycle stale

[xing-yang]

/milestone v1.25

[marosset]

Hello @ddebroy 👋, 1.25 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PST on Thursday June 16, 2022.

For note, This enhancement is targeting for stage alpha for 1.25 (correct me, if otherwise)

Here's where this enhancement currently stands:

• [ ] KEP file using the latest template has been merged into the k/enhancements repo.
• [ ] KEP status is marked as implementable
• [ ] KEP has a updated detailed test plan section filled out
• [ ] KEP has up to date graduation criteria
• [ ] KEP has a production readiness review that has been completed and merged into k/enhancements.

Looks like for this one, we would just need to update the following:

• Merge https://github.com/kubernetes/enhancements/pull/2893

For note, the status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[marosset]

Hello @ddebroy 👋, just a quick check-in again, as we approach the 1.25 enhancements freeze.

Please plan to get #2893 reviewed/merged before enhancements freeze (Thursday, June 23, 2022 at 18:00 PM PT).

For note, the current status of the enhancement is atat-risk. Thank you!

[ddebroy]

hi @marosset, after the KEP reviews and follow-up meetings around this feature with sig-storage leads, we are going to need more time around this to [1] incorporate the feedback around a runtime-generic mechanism for CSI plugins (using a proxy mechanism similar to Windows) so that each CSI plugin does not need to implement runtime-specific logic. [2] drive the CSI proposals required by this feature and outlined in the KEP in the CSI community. Based on the above, we will have to delay the Alpha for this to 1.26.

[marosset]

hi @marosset, after the KEP reviews and follow-up meetings around this feature with sig-storage leads, we are going to need more time around this to [1] incorporate the feedback around a runtime-generic mechanism for CSI plugins (using a proxy mechanism similar to Windows) so that each CSI plugin does not need to implement runtime-specific logic. [2] drive the CSI proposals required by this feature and outlined in the KEP in the CSI community. Based on the above, we will have to delay the Alpha for this to 1.26.

Thanks for the updates @ddebroy. If anything changes, please let me know.

[Priyankasaggu11929]

/milestone clear

[xing-yang]

/milestone v1.26

[parul5sahoo]

Hello @ddebroy 👋, 1.26 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2022.

This enhancement is targeting for stage alpha for 1.26 (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: 1.26
• [ ] KEP readme has a updated detailed test plan section filled out
• [ ] KEP readme has up to date graduation criteria
• [ ] KEP has a production readiness review that has been completed and merged into k/enhancements.

For this KEP, we would just need to complete all the tasks in the above list before the enhancements freeze in order to get the KEP included in the enhancement freeze.

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. And let us know if there are any queries. Thank you!

[parul5sahoo]

Hello @ddebroy just a quick remainder the enhancements freeze on 18:00 PDT on Thursday 6th October 2022.

[ddebroy]

We will need to explore the suggestion at https://github.com/kubernetes/enhancements/pull/2893#discussion_r988092284 with sig-node and that will take some more time as sig-node review bandwidth is quite low before the enhancements freeze. So at this point, this is most likely to spill to 1.27.

[parul5sahoo]

So, do I consider it as removed from milestone?

[rhockenbury]

/milestone clear /remove-label lead-opted-in /remove-label tracked/yes /label tracked/no

[npolshakova]

Hello @ddebroy 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023.

This enhancement is targeting for stage alpha for 1.27 (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: 1.27
• [ ] KEP readme has a updated detailed test plan section filled out
• [ ] KEP readme has up to date graduation criteria
• [ ] KEP has a production readiness review that has been completed and merged into k/enhancements.

For this KEP, we would just need to complete all the tasks in the above list before the enhancements freeze in order to get the KEP included in the enhancement freeze. It looks like https://github.com/kubernetes/enhancements/pull/2893 would address some of these issues.

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[ddebroy]

hi @npolshakova it looks like at this point this will have to wait till 1.28.

[mrunalp]

/milestone clear

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[vaibhav2107]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.