-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
OCPNODE-2213: Add support for Recursive Read-only (RRO) mounts #7962
OCPNODE-2213: Add support for Recursive Read-only (RRO) mounts #7962
Conversation
/assign kwilczynski |
@kwilczynski: This pull request references OCPNODE-2213 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
d3cb4b4
to
2a601c0
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #7962 +/- ##
==========================================
+ Coverage 49.17% 49.71% +0.54%
==========================================
Files 152 153 +1
Lines 16496 16704 +208
==========================================
+ Hits 8112 8305 +193
+ Misses 7394 7372 -22
- Partials 990 1027 +37 |
/retest-required |
2a601c0
to
324f0be
Compare
a83f3aa
to
ed947be
Compare
Signed-off-by: Krzysztof Wilczyński <kwilczynski@redhat.com>
Signed-off-by: Krzysztof Wilczyński <kwilczynski@redhat.com>
Signed-off-by: Krzysztof Wilczyński <kwilczynski@redhat.com>
Signed-off-by: Krzysztof Wilczyński <kwilczynski@redhat.com>
ed947be
to
0302c41
Compare
/retest |
@cri-o/cri-o-maintainers, please have a look again. Thank you! |
/test e2e-gcp-ovn |
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander, kwilczynski, sohankunkerkar 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 |
Signed-off-by: Krzysztof Wilczyński <kwilczynski@redhat.com>
105a81d
to
8cffb65
Compare
/lgtm |
/retest |
1 similar comment
/retest |
/cherry-pick release-1.29 |
@kwilczynski: #7962 failed to apply on top of branch "release-1.29":
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. |
OK. Requires manual cherry-pick. |
No need to cherry-pick this one as discussed. |
To add more background here: I initially thought we would need to backport this to 1.29, to support older Kubernetes and, as such, OpenShift. Thinking that we were missing some crucial functionality; however, this feature, as I remembered later, is only made available as Alpha in Kubernetes 1.30. Thus, there is no point in having any backports. |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Currently, the read-only option set for the host mounts does not correctly propagate recursively from the top level of the given mount point. As such, any sub-mounts that happen to be part of the tree would retain their current options, and should it be a read/write type mount, then it could be modified without any restriction. This is often both unexpected and undesirable.
Thus, add support for so-called Recursive Read-only (RRO) mounts. This allows a mount point to propagate the read-only option through the tree, marking the entire mount point read-only.
Support for the RRO mounts has already been available in the runtimes, such as crun and runc, for some time now.
Note
Support of the Recursive Read-only (RRO) mounts requires:
🔹⚠️ Feature gate called RecursiveReadOnlyMounts needs to be enabled given the Alpha status of the feature.
Related to:
Which issue(s) this PR fixes:
A temporary workaround:
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?