-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Recursive Read-only (RRO) mounts #3857
Comments
/sig node |
adding sig storage as participating sig /sig storage |
@AkihiroSuda do you want to target this KEP for 1.28? |
Not necessary. |
@kubernetes/sig-node-leads |
ping @kubernetes/sig-node-leads 🙏 |
@kubernetes/sig-node-leads |
cc @mrunalp @derekwaynecarr @dchen1107 @SergeyKanzhelev for the question above about v1.30 milestone |
+1 for v1.30
@SergeyKanzhelev do we have to check with sig storage leads about this KEP? |
@mrunalp @derekwaynecarr @dchen1107 @SergeyKanzhelev PTAL. |
@SergeyKanzhelev added sig storage as participating sig for this KEP. The proposal makes sense to me, but I still want to hear from the sig storage members. cc @jsafrane @msau42 @xing-yang Can you please review the proposal and provide your feedback? Thanks! If accepted, this KEP may be able to have an alpha implement in 1.30. |
Didn't get lead-opted-in. Giving up. Alternative: |
Reopening |
/milestone 1.30 |
@mrunalp: The provided milestone is not valid for this repository. Milestones in this repository: [ Use In response to this:
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. |
/milestone v1.30 |
With all the requirements fulfilled this enhancement is now marked as tracked for the upcoming enhancements freeze 🚀 |
Hi @AkihiroSuda , 👋 from the v1.30 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement! We encourage blogs for features including, but not limited to: breaking changes, features and changes important to our users, and features that have been in progress for a long time and are graduating. To opt in, you need to open a Feature Blog placeholder PR against the website repository. |
Hello @AkihiroSuda @johnbelamaric 👋, v1.30 Docs Shadow here. Does this enhancement work planned for v1.30 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.30 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, February 22nd, 2024 18:00 PDT Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you!
Reading the KEP, this requires a good amount of documentation, marking this as |
Opened a placeholder PR: |
Hey again @AkihiroSuda @johnbelamaric 👋 Enhancements team here, Just checking in as we approach code freeze at 02:00 UTC Wednesday 6th March 2024 . Here's where this enhancement currently stands:
For this enhancement, it looks like the following PRs are open and need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP):
Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. |
With the exception request being approved, this can now be marked as |
Hi @AkihiroSuda 👋, 1.31 Enhancements Lead here. If you wish to progress this enhancement in v1.31, please have the SIG lead opt-in your enhancement by adding the lead-opted-in label and set the milestone to v1.31 before the Production Readiness Review Freeze. /remove-label lead-opted-in |
@AkihiroSuda do you plan to progress it in 1.31? |
Yes, |
@kubernetes/sig-node-leads Could you lead-opt-in ? |
/milestone v1.31 |
Hello @AkihiroSuda 👋, 1.31 Enhancements team here. Just checking in as we approach enhancements freeze on on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024. This enhancement is targeting for stage Here's where this enhancement currently stands:
For this KEP, we would just need to update the following:
It looks like #4668 will address most of these issues.
The status of this enhancement is marked as If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you! |
Hi @AkihiroSuda 👋, 1.31 Enhancements team here, Just a quick friendly reminder as we approach the enhancements freeze later this week, at 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024. The current status of this enhancement is marked as If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you! |
Enhancement Description
One-line enhancement description (can be used as a release note): Recursive Read-only (RRO) mounts
Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/3857-rro-mounts
Discussion Link: none
Primary contact (assignee): @AkihiroSuda
Responsible SIGs: SIG-node
Enhancement target (which target equals to which milestone):
Alpha
k/enhancements
) update PR(s): KEP-3857: Recursive Read-only (RRO) mounts #3858k/k
) update PR(s):k/website
) update PR(s):Beta
k/enhancements
) update PR(s): KEP-3857: Recursive Read-only (RRO) mounts: promote to Beta #4668k/k
) update PR(s):k/website
) update(s):Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
The text was updated successfully, but these errors were encountered: