-
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
Support for Windows privileged containers #1981
Comments
/sig windows |
/sig node |
/kind feature |
/stage alpha |
@ambguo: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility. 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. |
/stage alpha |
@immuzz: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility. 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. |
Hi all, Enhancements Lead here. Will just update the milestone for you 😄 Best, |
Just as a note when you convert your KEP don't forget to also include the kep.yaml Both templates that you will need can be found here: Please also update the description when you make the PR and please link any other PRs so that this enhancement can be tracked to the milestone. Hope that helps. Best, |
Hi @ambguo, Enhancement shadow for 1.20 release here 👋. Just wanted to check if you had a chance to convert KEP according to the template posted above (https://github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template). Please note that the Enhancement freeze deadline for KEPs to be included in 1.20 milestone is Your proposal looks great 😄, could you please include the following when you make the KEP PR:
Thank you! |
Thank you @ambguo for actively working on the KEP PR! Here's the status update based on the freeze requirements:
Just a friendly reminder that we'd need all of them with ✅ status to be included in 1.20 milestone by Enhancement Freeze deadline Ping me anytime on slack ( Thank you!! |
/milestone v1.21 |
@kinarashah: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility. 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. |
@marosset i thought we are doing privileged containers as alpha for v1.20, not 1.21 |
@michmike from our discussion on Tuesday, we are looking into ways to address the pod networking issues mentioned. We are still investigating ways to address the challenges, so will not be able to pursue the alpha release in 1.20 since APIs may require changes depending on the solution. |
This is now marked as |
I recommend cracking on with early work on a docs update so that these are GA quality (or have PRs open to make them be) by the appropriate review deadline. |
I started a draft docs PR (linked in initial issue description) and will add more updates as soon as I finish up the e2e coverage that is listed as graduation criteria for this enhancement. |
Thanks for that early start! |
blog placeholder PR - kubernetes/website#37370 |
Hi @marosset 👋, Checking in as we approach 1.26 code freeze at 17:00 PDT on Tuesday 8th November 2022. Please ensure the following items are completed:
For this enhancement, it looks like the following PRs are open and need to be merged before code freeze: As always, we are here to help should questions come up. Thanks! |
Hello @marosset 👋, 1.26 Release Docs Lead here. This enhancement is marked as ‘Needs Docs’ for 1.26 release. Please follow the steps detailed in the documentation to open a PR against Any doubt, reach us! Thank you! |
@krol3 I have a placeholder docs PR open and linked in the issue description :) |
Hi @marosset ! how are you? I see a PR placeholder for the blog, I think we need an update in the documentation too. |
I've got 2 place-holder PRs open against k/website for this feature Let me know if there is anything else needed at this time. I'm going to work on both of these after 1.26 code-freeze. |
With kubernetes/kubernetes#113476 merged, I have this marked as |
Hello @marosset 👋 please take a look at Documenting for a release - PR Ready for Review to get your PR ready for review before deadline Tuesday 15th November 2022. Thank you! |
/close This KEP is now fully implemented. |
@marosset: Closing this issue. 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. |
Enhancement Description
One-line enhancement description (can be used as a release note): Windows privileged container support and host networking support.
Kubernetes Enhancement Proposal: 1981-windows-privileged-containers
Primary contact (assignee): @marosset
Responsible SIGs: sig-windows, sig-node
Enhancement target (which target equals to which milestone):
Alpha
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s):Beta
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s):Stable
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update(s):The text was updated successfully, but these errors were encountered: