-
Notifications
You must be signed in to change notification settings - Fork 1.5k
KEP-4639: Allow writeable, container isolated volume content #5288
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
base: master
Are you sure you want to change the base?
KEP-4639: Allow writeable, container isolated volume content #5288
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: saschagrunert The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
d5b7133
to
687d127
Compare
687d127
to
ddb30d6
Compare
ddb30d6
to
32ab875
Compare
32ab875
to
c3b24aa
Compare
bd7a285
to
fd5c3bc
Compare
This proposal changes the KEP to allow writing the image volume contents in the same way as we already support it for the actual running container image. Runtimes have to ensure that the isolation is restricted to the running container by using technologies like overlayfs. Signed-off-by: Sascha Grunert <[email protected]>
fd5c3bc
to
2d4ec5e
Compare
/retest |
This proposal changes the KEP to allow writing the image volume contents in the same way as we already support it for the actual running container image. Runtimes have to ensure that the isolation is restricted to the running container by using technologies like overlayfs.
Refers to #4639, kubernetes/kubernetes#131557, cri-o/cri-o#9174
PTAL @kubernetes/sig-node-feature-requests @mikebrow @haircommander