/sig node

adding sig storage as participating sig

/sig storage

@AkihiroSuda do you want to target this KEP for 1.28?

@AkihiroSuda do you want to target this KEP for 1.28?

Not necessary.

@kubernetes/sig-node-leads
Any chance to get this lead-opted-in for v1.29?

ping @kubernetes/sig-node-leads 🙏

@kubernetes/sig-node-leads
Will this be considered for lead-opted-in in the v1.30 milestone?

cc @mrunalp @derekwaynecarr @dchen1107 @SergeyKanzhelev for the question above about v1.30 milestone

+1 for v1.30

• We may tag this as v1.30 and get some early input.

adding sig storage as participating sig

@SergeyKanzhelev do we have to check with sig storage leads about this KEP?

@mrunalp @derekwaynecarr @dchen1107 @SergeyKanzhelev

PTAL.
If this KEP isn't going to be accepted, I'll just modify the default behavior of containerd to treat "readonly" as "recursive readonly".
Small portion of users may find this to be a breaking change, but probably this is subtle enough.
#3858 (comment)

@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:

• [Reverted in #9747] cri: make read-only mounts recursively read-only containerd/containerd#9713

Reopening

#3858 (comment)

/milestone 1.30
/stage alpha
/label lead-opted-in

@mrunalp: The provided milestone is not valid for this repository. Milestones in this repository: [v1.25, v1.27, v1.28, v1.29, v1.30, v1.31]

Use /milestone clear to clear the milestone.

/milestone v1.30

Hello @AkihiroSuda 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 9th February 2024.

This enhancement is targeting for stage alpha for v1.30 (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.30.
• 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).

For this KEP, we would just need to update the following:

• The production readiness review should be completed. One question appears unanswered.
• Make sure the PR with the information get merged before enhancement freeze, I just found this PR.

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

KEP readme using the latest template has been merged into the k/enhancements repo.

Updated to the latest template

The production readiness review should be completed. One question appears unanswered.

Answered.

Thank you. I will move it from At Risk when the PR gets merged.

Draft PRs:

• KEP-3857: Recursive Read-only (RRO) mounts  kubernetes#123180
• KEP-3857: Recursive Read-only (RRO) mounts kubernetes-sigs/cri-tools#1344
• KEP-3857: Recursive Read-only (RRO) mounts containerd/containerd#9787

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.
The placeholder PR deadline is 27th February, 2024.
Here's the 1.30 Release Calendar

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!

Does this enhancement work planned for v1.30 require any new docs or modification to existing docs?

Reading the KEP, this requires a good amount of documentation, marking this as Need Docs. Thanks!

docs

Here:

• [dev-1.30] KEP-3857: Recursive Read-only (RRO) mounts website#45159

To opt in, you need to open a Feature Blog placeholder PR against the website repository. The placeholder PR deadline is 27th February, 2024. Here's the 1.30 Release Calendar

Opened a placeholder PR:

• blog post for KEP-3857: Recursive Read-only (RRO) mounts website#45238

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:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

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):

• KEP-3857: Recursive Read-only (RRO) mounts  kubernetes#123180
• KEP-3857: Recursive Read-only (RRO) mounts kubernetes-sigs/cri-tools#1344

Also, please let me know if there are other PRs in k/k we should be tracking for this KEP.
As always, we are here to help if any questions come up. Thanks!

With the exception request being approved, this can now be marked as tracked for code freeze.