-
Notifications
You must be signed in to change notification settings - Fork 459
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
KEP-3857: Recursive Read-only (RRO) mounts #1344
Conversation
674c5ad
to
eb84fe5
Compare
@AkihiroSuda is this required as part of the KEP merge? Just trying to gauge priority and if we should get some reviews before freeze? |
cri-tools has a less strict release cycle than kubernetes. We can merge this after kubernetes freeze if we need to. |
containerd/containerd#9787 was already merged, so we'd like to see this critest to be available in the upstream soon |
Rebased |
This failure is an issue of CRI-O (it reports that it implements RRO, but actually it does not) |
51dbdb3
to
e853e41
Compare
I'm going to rebuild the CRI-O bundle in https://github.com/cri-o/packaging/actions/runs/8096897942, after that the CI should pick-up the merge of cri-o/cri-o#7828 Edit: Done ✔️ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one nit, otherwise LGTM
See kubernetes/enhancements issue 3857 (PR 3858) Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: AkihiroSuda, saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Depends on:
Depended by:
What type of PR is this?
/kind feature
What this PR does / why we need it:
Implement KEP-3857: Recursive Read-only (RRO) mounts
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
Does this PR introduce a user-facing change?