-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
Document user namespace changes in v1.27 (KEP-127) #39860
Conversation
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
Remember to change the base branch and target the |
@reylejano thanks, fixed that now! |
Hi @rata 👋 please take a look at Documenting for a release - PR Ready for Review to get your PR ready for review as soon as possible. 01:00 UTC Wednesday 22nd March 2023 / 17:00 PDT Tuesday 21st March 2023 is the official deadline. This PR will need a doc review by Tuesday 4th April 2023 to get this into the release. Please reach out to required SIGs to get their review. Thank you! |
c0bd517
to
cb8701e
Compare
@mickeyboxell thanks, this should be ready for review now! |
content/en/docs/tasks/configure-pod-container/user-namespaces.md
Outdated
Show resolved
Hide resolved
Pushed a new revision, PTAL |
/label tide/merge-method-squash |
LGTM label has been added. Git tree hash: 7b641c7f1ad38026c10fdaab06d84eb4583e7d30
|
@tengqm Can you PTAL? I've added a new commit duplicating a warning about versions. It seems it is better to be super clear about this and not have it only in some pages and not others. I'm trying to err on the side of being very clear as a learning from another (not related to this) bug report where doc was the issue. Did it as another commit, also, as you selected the squash merge method |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tengqm 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 |
@tengqm thanks, now the lgtm is missing :-D |
👷 Deploy Preview for kubernetes-io-vnext-staging processing.
|
Updated this PR to address similar comments that were raised in this other PR and also applied here: #40264 |
|
||
* The filesystem you use for `/var/lib/kubelet/pods/`, or the custom directory | ||
you configure for this, needs idmap mount support. | ||
* All the filesystems used in the pod need support for idmap mounts. |
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.
* All the filesystems used in the pod need support for idmap mounts. | |
* Every volume that is mounted into any container in the pod must support idmap mounts. |
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.
This smells slightly incorrect. What supports idmap mount is the filesystem, not the volume. It doesn't matter if it is an EBS volume, a local disk volume or what. The only thing that matters is that the filesystem used in that volume supports idmap mounts in the kernel running on the host.
So, what about this instead?
* All the filesystems used in the pod's volumes must support idmap mounts.
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.
Changed it to that, let me know what you think
content/en/docs/tasks/configure-pod-container/user-namespaces.md
Outdated
Show resolved
Hide resolved
@sftim fixed all, thanks! PTAL |
Also, with the new implementation, the fsGroup was dropped. So removed the mention to those limitations. Signed-off-by: Rodrigo Campos <[email protected]>
Signed-off-by: Rodrigo Campos <[email protected]>
/lgtm |
LGTM label has been added. Git tree hash: 47c8f361630764ce0c0d919700424947b8306475
|
* content: Update user namespaces version requirements Also, with the new implementation, the fsGroup was dropped. So removed the mention to those limitations. Signed-off-by: Rodrigo Campos <[email protected]> * content: Add reference to the userns task in the concepts page Signed-off-by: Rodrigo Campos <[email protected]> --------- Signed-off-by: Rodrigo Campos <[email protected]>
Placeholder PR to document the changes in Kubernetes v1.27 for user namespaces (KEP-127)
cc @giuseppe