-
Notifications
You must be signed in to change notification settings - Fork 1.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
Fine-grained SupplementalGroups control #3619
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
@everpeace: The label(s) 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. |
This comment was marked as off-topic.
This comment was marked as off-topic.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
/milestone v1.27 let's see if we can start it in 1.27 |
/label lead-opted-in |
/stage alpha |
Hello @everpeace 👋, 1.27 Enhancements team here. Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023. This enhancement is targeting for stage Here's where this enhancement currently stands:
It looks like #3620 will address most of these issues. The status of this enhancement is marked as |
@npolshakova, kep yaml has correct values for stage, milestone, etc:
This KEP updates to the latest template and covers testing section: #3862 PRR review completed: enhancements/keps/prod-readiness/sig-node/3619.yaml Lines 1 to 6 in 472a381
So once #3862 is merged, this KEP is ready for the milestone |
Great! Looks like #3862 went in so this enhancement as tracked for v1.27. /label tracked/yes |
/remove-lifecycle stale |
@kubernetes/sig-node-leads Recently, I have been working (rebooted) on this KEP actively to target v1.31.
Could we get this KEP opt-in for v1.31? WDYT? |
@mrunalp or @dchen1107 or delegate - are you OK to lead opt-in ? |
/label lead-opted-in |
Hello @everpeace 👋, Enhancements team here. Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024. This enhancement is targeting stage Here's where this enhancement currently stands:
All the KEP requirements are in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀 The status of this enhancement is marked as |
@everpeace Docs team here. Can you create a PR for the documentation for this enhancement? |
Hi @everpeace, 👋 from the v1.31 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement! To opt in, let us know and open a Feature Blog placeholder PR against the website repository by 3rd July, 2024. For more information about writing a blog see the blog contribution guidelines. Note: In your placeholder PR, use |
Thanks, I opened a draft PR for this KEP: kubernetes/website#46920 |
Thanks, I'm happy to write a blog for this KEP. I opened a placeholder PR: kubernetes/website#46921 |
Hey again @everpeace 👋, Enhancements team here, Just checking in as we approach code freeze at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024. Here's where this enhancement currently stands:
Regarding this enhancement, it appears that there are currently 2 open PRs in the k/k repository out of which one is merged and the other is up for review. For this KEP, we would need to do the following:
If you anticipate missing code freeze, you can file an exception request in advance. The status of this enhancement is currently marked as |
@thockin @mrunalp @SergeyKanzhelev (as KEP reviwers/approvers) I apologize for bothering you again. As you may already be aware, my last k/k PR kubernetes/kubernetes#125470 (review) for this KEP is ready for review. I would be very grateful if this KEP could reach alpha in v1.31🙇. |
Hey again @everpeace 👋, 1.31 Enhancements team here, Just a quick friendly reminder as we approach code freeze in about 2 days, at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024. The current status of this enhancement is marked as at risk for code freeze. A few requirements mentioned in the comment #3619 (comment) still need to be completed. The following PR as per the description still needs to be merged: If you anticipate missing code freeze, you can file an exception request in advance. |
Whether the containerd PR is merged or not shouldn't matter here - their release train is async to ours anyway. @ArkaSaha30 tell me if you disagree? |
Yes, agree. Thank you for the clarification. |
Thanks, I updated this Issue's description to make containerd/CRI-O PRs optional. updated: all the optional PR are merged now 👍 The remaining part is just doc and blog. |
Enhancement Description
PodSecurityContext.SupplementalGroups
by custom container image although PSP(or other policy engines) enforces the field kubernetes#112879k/enhancements
) update PR(s):SupplementalGroupsPolicy
feature fields in Kubernetes API(Node.Status
) and CRI(RuntimeStatusResponse
) #4728k/k
) update PR(s):k/website
) update PR(s):Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
/assign
/sig node
/kind feature
The text was updated successfully, but these errors were encountered: