Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ReadWriteOncePod PersistentVolume Access Mode #2485

Open
7 of 8 tasks
chrishenzie opened this issue Feb 10, 2021 · 27 comments · May be fixed by #3537
Open
7 of 8 tasks

ReadWriteOncePod PersistentVolume Access Mode #2485

chrishenzie opened this issue Feb 10, 2021 · 27 comments · May be fixed by #3537
Assignees
Labels
sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team

Comments

@chrishenzie
Copy link
Member

chrishenzie commented Feb 10, 2021

Enhancement Description

/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.

@k8s-ci-robot k8s-ci-robot added the sig/storage Categorizes an issue or PR as relevant to SIG Storage. label Feb 10, 2021
@chrishenzie chrishenzie changed the title Single pod, single node PersistentVolume AccessMode Strict RWO PersistentVolume AccessMode Feb 10, 2021
@JamesLaverack
Copy link
Member

JamesLaverack commented Apr 28, 2021

/milestone v1.22

@k8s-ci-robot k8s-ci-robot added this to the v1.22 milestone Apr 28, 2021
@JamesLaverack JamesLaverack added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status labels Apr 28, 2021
@chrishenzie chrishenzie changed the title Strict RWO PersistentVolume AccessMode ReadWriteOncePod PersistentVolume Access Mode May 11, 2021
@PI-Victor
Copy link
Member

PI-Victor commented May 18, 2021

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
Copy link
Member Author

chrishenzie commented May 25, 2021

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

@supriya-premkumar
Copy link
Contributor

supriya-premkumar commented Jun 22, 2021

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
Copy link
Member Author

chrishenzie commented Jun 22, 2021

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
Copy link
Contributor

supriya-premkumar commented Jun 22, 2021

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

@chrishenzie
Copy link
Member Author

chrishenzie commented Jun 22, 2021

Hi @supriya-premkumar , they are:

I added these to the checklist in the description above

@chrishenzie
Copy link
Member Author

chrishenzie commented Jun 22, 2021

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
Copy link
Contributor

supriya-premkumar commented Jun 22, 2021

Thank you for the update @chrishenzie!

@chrishenzie
Copy link
Member Author

chrishenzie commented Jun 24, 2021

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
Copy link
Contributor

supriya-premkumar commented Jun 25, 2021

No worries at all. Thanks for letting me know.

@supriya-premkumar
Copy link
Contributor

supriya-premkumar commented Jul 2, 2021

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
Copy link
Member Author

chrishenzie commented Jul 2, 2021

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

@supriya-premkumar
Copy link
Contributor

supriya-premkumar commented Jul 2, 2021

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

@salaxander salaxander added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Aug 19, 2021
serathius added a commit to serathius/enhancements that referenced this issue Sep 8, 2021
serathius added a commit to serathius/enhancements that referenced this issue Sep 8, 2021
k8s-ci-robot pushed a commit that referenced this issue Sep 9, 2021
* Move KEP-2845 to implementable

* Add PRR for #2845

* Remove mention of --logtostdout flag in #2845

* KEP #2485: Require splitting stdout/stderr to Json format

* Add pohly as reviewer for KEP 2845

* #2845 Update PRR

* #2845 Add dims as SIG arch approver
@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 16, 2022
@k8s-triage-robot
Copy link

k8s-triage-robot commented May 17, 2022

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 17, 2022
@chrishenzie
Copy link
Member Author

chrishenzie commented May 17, 2022

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 17, 2022
@k8s-triage-robot
Copy link

k8s-triage-robot commented Aug 15, 2022

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 15, 2022
@xing-yang
Copy link
Contributor

xing-yang commented Sep 14, 2022

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 14, 2022
@xing-yang xing-yang added the lead-opted-in Denotes that an issue has been opted in to a release label Sep 14, 2022
@xing-yang xing-yang modified the milestones: v1.22, v1.26 Sep 14, 2022
@xing-yang xing-yang added stage/beta Denotes an issue tracking an enhancement targeted for Beta status and removed stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status labels Sep 14, 2022
@rhockenbury rhockenbury added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Sep 20, 2022
@parul5sahoo
Copy link
Member

parul5sahoo commented Sep 22, 2022

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
Copy link
Member

alculquicondor commented Sep 22, 2022

/sig scheduling

@k8s-ci-robot k8s-ci-robot added the sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. label Sep 22, 2022
@chrishenzie
Copy link
Member Author

chrishenzie commented Sep 22, 2022

Submitted #3537 for beta graduation and updated issue description

@msau42 msau42 linked a pull request Sep 22, 2022 that will close this issue
@chrishenzie
Copy link
Member Author

chrishenzie commented Sep 22, 2022

Beta graduation will need to happen in 1.27, see here for more context: #3537 (comment)

Updated the KEP target and issue description.

@rhockenbury
Copy link

rhockenbury commented Sep 29, 2022

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

@k8s-ci-robot k8s-ci-robot added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Sep 29, 2022
@k8s-ci-robot k8s-ci-robot removed this from the v1.26 milestone Sep 29, 2022
@k8s-ci-robot k8s-ci-robot removed the lead-opted-in Denotes that an issue has been opted in to a release label Sep 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
Status: Graduating
Development

Successfully merging a pull request may close this issue.