Enhancements: Support for Windows privileged containers

Created on 11 Sep 2020  ยท  18Comments  ยท  Source: kubernetes/enhancements

Enhancement Description

  • One-line enhancement description (can be used as a release note): Windows privileged container support and host networking support.
  • Kubernetes Enhancement Proposal: proposal (will be converted to md file under Kubernetes enhancements)
  • Primary contact (assignee): @ambguo
  • Responsible SIGs: sig-windows, sig-node
  • Enhancement target (which target equals to which milestone):

    • Alpha release target (1.20)

    • Beta release target (1.21)

    • Stable release target (1.22 or later)

kinfeature sinode siwindows stagalpha trackeno

Most helpful comment

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 Tuesday, October 6.

Your proposal looks great ๐Ÿ˜„, could you please include the following when you make the KEP PR:

  • Add test plans
  • Update graduation criteria (you've already mentioned those, but if you could update/confirm it for 1.20, that'd be great!)
  • Update state to implementable

Thank you!

All 18 comments

/sig windows

/sig node

/kind feature

/stage alpha
/milestone v1.20

@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:

/stage alpha
/milestone v1.20

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
/milestone v1.20

@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:

/stage alpha
/milestone v1.20

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.

cc: @marosset @michmike @ddebroy @jsturtevant

Hi all,

Enhancements Lead here. Will just update the milestone for you :smile:

Best,
Kirsten

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:
https://github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template

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,
Kirsten

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 Tuesday, October 6.

Your proposal looks great ๐Ÿ˜„, could you please include the following when you make the KEP PR:

  • Add test plans
  • Update graduation criteria (you've already mentioned those, but if you could update/confirm it for 1.20, that'd be great!)
  • Update state to implementable

Thank you!

Thank you @ambguo for actively working on the KEP PR!

Here's the status update based on the freeze requirements:

Requirement | Status | Comments
-------- | ------ | ------
Test Plan | โ— | missing test plans for alpha
Graduation Criteria | โ— | confirm milestone to 1.20 for alpha here. Beta's set to 1.20+.
Implementable State | โ— | add KEP yaml with state implementable as mentioned here. If you're looking for an example, hopefully this recently merged sig node kep yaml gives you an idea.
Merged | โ— |

Just a friendly reminder that we'd need all of them with โœ… status to be included in 1.20 milestone by Enhancement Freeze deadline Tuesday, October 6.

Ping me anytime on slack (kinarashah) or here if you have any questions ๐Ÿ˜„.

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:

/milestone v1.21

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.

Spoke with @marosset and @ambguo, this will be tracked alpha for 1.21 milestone and KEP PR would be merged in provisional status for now.

@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.

@ambguo can you please update the description on this issue to point to the KEP, rather than the draft in Gdocs?

Was this page helpful?
0 / 5 - 0 ratings

Related issues

majgis picture majgis  ยท  5Comments

prameshj picture prameshj  ยท  9Comments

xing-yang picture xing-yang  ยท  13Comments

saschagrunert picture saschagrunert  ยท  6Comments

boynux picture boynux  ยท  3Comments