KEP-4639: Allow writeable, container isolated volume content#5288
KEP-4639: Allow writeable, container isolated volume content#5288saschagrunert wants to merge 1 commit intokubernetes:masterfrom
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. DetailsNeeds 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 <sgrunert@redhat.com>
fd5c3bc to
2d4ec5e
Compare
|
/retest |
|
PR needs rebase. DetailsInstructions 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-sigs/prow repository. |
|
@haircommander @bitoku do we still need/want this? |
|
personally I think we should extend the image volume API to include a readOnly field and use that to determine RO status, instead of opaquely leaving it up to the CRI |
|
The plan is now to GA with read-only volumes and extend the API as follow-up KEP. |
|
Can we keep this open until the follow up kep is created and linked? |
I linked it in the main KEP as follow-up: #4639 (comment) |
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