ReadWriteOncePod PersistentVolume Access Mode

[chrishenzie]

Enhancement Description

• One-line enhancement description (can be used as a release note): ReadWriteOncePod PersistentVolume Access Mode
• Kubernetes Enhancement Proposal: KEP-2485: ReadWriteOncePod PV Access Mode
• Discussion Link: CSI community meeting, timestamped at 8m8s when topic is discussed
• Primary contact (assignee): @chrishenzie
• Responsible SIGs: sig-storage, sig-scheduling
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.22
  • Beta release target (x.y): 1.27
  • Stable release target (x.y): TBD
• [X] Alpha
  • [X] KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/2489
  • [X] Code (k/k) update PR(s): https://github.com/kubernetes/kubernetes/pull/102894, https://github.com/kubernetes/kubernetes/pull/102028, https://github.com/kubernetes/kubernetes/pull/103082
  • [X] Docs (k/website) update PR(s): https://github.com/kubernetes/website/pull/28114
• [X] Beta
  • [X] KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/3537
  • [x] Code (k/k) update PR(s): https://github.com/kubernetes/kubernetes/pull/114051
  • [ ] Docs (k/website) update(s):

/sig storage /sig scheduling

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

[JamesLaverack]

/milestone v1.22

[PI-Victor]

Hello @chrishenzie 👋, 1.22 Docs release lead here. This enhancement is marked as ‘Needs Docs’ for 1.22 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.22 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Fri July 9, 11:59 PM PDT.
 Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release. 
Thank you!

p.s.: please don't forget to add PersistentVolumeAccessMode to the feature gates table to reflect this change.

[chrishenzie]

Hello @PI-Victor, I drafted a PR for kubernetes/website here. Thanks!

[supriya-premkumar]

Hi @chrishenzie. This is Supriya, 1.22 Enhancements Shadow here.

Code Freeze is on July 8th 2021 @ EOD PST. All tracked enhancements must be code complete, merged and have docs PRs open. Please link your k/k PRs to the k/enhancements, so that they can be tracked going into freeze. If PRs are not merged by code freeze, they will be removed from the 1.22 milestone.

Please let us know on the PR link/status. Thank you!

[chrishenzie]

Hi @supriya-premkumar , thanks for the reminder. Just updated the description to include links the PRs for K8s changes + the website.

Currently undergoing API review for the new access mode. I opened a separate PR for scheduler changes to support this feature.

[supriya-premkumar]

Hi @chrishenzie, thank you for letting us know. Could you please link the related PRs? It will be helpful to track them.

[chrishenzie]

Hi @supriya-premkumar , they are:

• https://github.com/kubernetes/kubernetes/pull/102894
• https://github.com/kubernetes/kubernetes/pull/102028
• https://github.com/kubernetes/kubernetes/pull/103082

I added these to the checklist in the description above

[chrishenzie]

Hi @supriya-premkumar , quick update: I've updated the description above to remove the third PR. We plan on targeting this feature for beta to allow more time for development + design.

[supriya-premkumar]

Thank you for the update @chrishenzie!

[chrishenzie]

Hi @supriya-premkumar , sorry for the churn here. I re-added the third PR; sig scheduling recommends this makes it in for alpha. It should be good to go (once the base PR is merged).

[supriya-premkumar]

No worries at all. Thanks for letting me know.

[supriya-premkumar]

Hi @chrishenzie, just a reminder that we are one week away from the code freeze(July 8th, 2021) and with all the three k/k PRs merged(102894, 102028, 103082) this issue is now on track for the 1.22 release 🎉

Also, the Doc Placeholder PR deadline is on July 9th, 2021.

[chrishenzie]

Hi @supriya-premkumar , thanks for the update. The placeholder PR is open, does it need to be fully populated by that deadline?

[supriya-premkumar]

For the Doc Placeholder PR, it does not need to be fully populated.

[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

[chrishenzie]

/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

[chrishenzie]

/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

[chrishenzie]

/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

[xing-yang]

/remove-lifecycle stale

[parul5sahoo]

Hello @chrishenzie 👋, 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 beta 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 update the following:

• update the test plan section according to the latest template and add the agreement.
• update the stage and latest milestone to beta and 1.26 in the kep.yaml
• Complete and merge the PRR for beta stage.

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

[alculquicondor]

/sig scheduling

[chrishenzie]

Submitted https://github.com/kubernetes/enhancements/pull/3537 for beta graduation and updated issue description

[chrishenzie]

Beta graduation will need to happen in 1.27, see here for more context: https://github.com/kubernetes/enhancements/pull/3537#discussion_r978120310

Updated the KEP target and issue description.

[rhockenbury]

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

[marosset]

Hello @chrishenzie 👋, 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 beta for v1.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: v1.27
• [ ] KEP readme has a updated detailed test plan section filled out
• [x] 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 enhancement, it looks like https://github.com/kubernetes/enhancements/pull/3537 will address all of the remaining requirements.

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!

[chrishenzie]

/reopen Leaving open to track progress. PRR approved. Working on merging scheduler changes required for beta.

[k8s-ci-robot]

@chrishenzie: Reopened this issue.

In response to this:

/reopen Leaving open to track progress. PRR approved. Working on merging scheduler changes required for beta.

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.