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
[release-1.27] server: allow Bidirectional mounts that contain storage root #7457
[release-1.27] server: allow Bidirectional mounts that contain storage root #7457
Conversation
…age root Signed-off-by: Harshal Patil <harpatil@redhat.com>
previously we would never allow a container to get anything other than HostToContainer for something that contains the storage root. This breaks situations where the container wishes to update mount points within the container and see them propegated to the host. Instead, we should only override this if the mount is Private. Signed-off-by: Peter Hunt <pehunt@redhat.com>
@kwilczynski: This pull request explicitly references no jira issue. 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. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## release-1.27 #7457 +/- ##
================================================
+ Coverage 49.30% 49.31% +0.01%
================================================
Files 128 128
Lines 15187 15196 +9
================================================
+ Hits 7488 7494 +6
- Misses 6801 6803 +2
- Partials 898 899 +1 |
/lgtm |
@kwilczynski: you cannot LGTM your own PR. 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. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kwilczynski, 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 |
hm why did we backport this? was someone asking for this behavior? I worry about having introduced more issues (even past the one that is now fixed) and I'm not sure we should introduce such instability into this branch |
Hi @haircommander,
What do you mean when you say "instability"? Do you foresee issues? I am asking as we backported this to release 1.28, and we are about to cut a 1.28.2 release. Similarly, with 1.27.2 - it was with anticipation of this new release and the fact that we made a backport to a different release branch I decided to backport this fix. Both are our active releases, and this fixes issues with some CSI that people use. If we weren't entirely sure about this, why backport to 1.28 and not just leave it on the main branch? Nevertheless, we can revert before you cut the 1.27.2 release. 😄 |
FWIW: the initial commit here is kind of a feature. It fixes an issue when users mount /host and aren't able to see updates to /var/lib/containers. that said, I think it's fine. let's leave it for now |
This is a manual cherry-pick of #7076 and #7408
/assign kwilczynski