Exception for KEP-3857: Recursive Read-only (RRO) mounts

160 views
Skip to first unread message

Akihiro Suda

unread,
Mar 6, 2024, 1:17:35 AMMar 6
to kubernete...@googlegroups.com, releas...@kubernetes.io, kubernetes-...@googlegroups.com
- Enhancement name: Recursive Read-only (RRO) mounts
- Enhancement status (alpha/beta/stable): alpha
- SIG: Node
- k/enhancements repo issue #: https://github.com/kubernetes/enhancements/pull/3857
- PR #’s: https://github.com/kubernetes/kubernetes/pull/123180
  The feature implementation is complete with a good amount of unit tests and E2E tests,
  but this still needs a trivial fix for feature-gating the output of `k get nodes`.
- Additional time needed (in days): 3
- Reason this enhancement is critical for this milestone: The feature is already implemented by containerd and critest, so Kubernetes releases should be synced with them.
- Risks from adding code late: low, as this feature-gated and disabled by default
- Risks from cutting enhancement: users will have to continue using insecure mounts if the enhancement is going to be cut

Kat Cosgrove

unread,
Mar 6, 2024, 1:21:30 PMMar 6
to Akihiro Suda, kubernete...@googlegroups.com, releas...@kubernetes.io, kubernetes-...@googlegroups.com
Hi all,

Following discussion in Slack, the release team is APPROVING this exception request. Your updated deadline to merge all open code implementation PRs and docs for your KEP is 18:00 PST Friday, 8th March 2024.

If you need any clarification, please reach out to us in the #sig-release Slack channel.

Thanks,
Kat Cosgrove
1.30 Release Team Lead

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-re...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-release/CAG8fp8RkvEyPOoH5Tyyod7XFmMj6E1vouS%2BQjL2qJx-P9XomHg%40mail.gmail.com.

Akihiro Suda

unread,
Mar 8, 2024, 10:07:04 PMMar 8
to Kat Cosgrove, kubernete...@googlegroups.com, releas...@kubernetes.io, kubernetes-...@googlegroups.com
Thank you for approving the exception request.
The PR is ready to be merged, and got /approve for node, but it is not merged yet:
https://github.com/kubernetes/kubernetes/pull/123180

Any chance to extend the deadline for while to wait for merging?

2024年3月7日(木) 3:21 Kat Cosgrove <kat.co...@gmail.com>:

Kat Cosgrove

unread,
Mar 9, 2024, 12:05:13 PMMar 9
to Akihiro Suda, kubernetes-sig-node, releas...@kubernetes.io, kubernetes-sig-release
Hi,

The code freeze deadline does require the actual merging of your code.

I've updated the thread in the #sig-release channel for discussion with all relevant parties. :)

Akihiro Suda

unread,
Mar 9, 2024, 12:22:20 PMMar 9
to Kat Cosgrove, kubernetes-sig-node, releas...@kubernetes.io, kubernetes-sig-release
Thank you!

2024年3月10日(日) 2:05 Kat Cosgrove <kat.co...@gmail.com>:
Reply all
Reply to author
Forward
0 new messages