Thow an error if the kubelet requests mounts with uid/gid mappings#8376
Conversation
We will use this in future commits to see if the kubelet requested idmap mounts for volumes, that we don't yet support. Signed-off-by: Rodrigo Campos <[email protected]>
|
Hi @rata. Thanks for your PR. I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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/test-infra repository. |
1f36a46 to
51b6ff6
Compare
|
Re pushing to kick the CI again due to the flaky test failed on windows |
We need support in containerd and the OCI runtime to use idmap mounts. Let's just throw an error for now if the kubelet requests some mounts with mappings. Signed-off-by: Rodrigo Campos <[email protected]>
51b6ff6 to
7e6ab84
Compare
This PR implements option 1 of the possible solutions described here: #8209.
This PR just throws an error to avoid possible problems in the future (explained in the issue). But support for idmap mounts on volumes (not the rootfs) is coming in this PR: #8287
Once this is merged in main, I'll backport it to 1.7 as that is the only release affected. It was suggested to merge it in main by @fuweid here
Fixes: #8209