Host network support for Windows pods

[marosset]

Enhancement Description

• One-line enhancement description (can be used as a release note): Host network support for Windows pods

• Kubernetes Enhancement Proposal: (https://github.com/kubernetes/enhancements/tree/master/keps/sig-windows/3503-host-network-support-for-windows-pods)

• Discussion Links:
  Discussed at the SIG-Windows community meetinig on 9/13/2022 - https://youtu.be/gC3lWMtP0-I?t=595
  Discussed with SIG-Node at the 9/13/2022 community meeting - meeting notes
  Discussed with SIG-Network at the 9/15/2022 community meeting - meeting notes

• Primary contact (assignee): marosset

• Responsible SIGs: Windows, Node, Network

• Enhancement target (which target equals to which milestone):

  • Alpha release target (x.y): 1.26
  • Beta release target (x.y):
  • Stable release target (x.y):

• Alpha

  • KEP (k/enhancements) update PR(s):
    • KEP-3503 Initial KEP for windows host-network support #3507
  • Code (k/k) update PR(s):
    • Windows hostnetwork alpha kubernetes#112961
  • Docs (k/website) update PR(s):
    • WindowsHostNetwork alpha updates website#37672

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[k8s-ci-robot]

@marosset: There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

• /sig <group-name>
• /wg <group-name>
• /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

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]

/sig node network
/label lead-opted-in

[kikisdeliveryservice]

@marosset please provide a Discussion Link. It is required that you "link to SIG mailing list thread, meeting, or recording where the Enhancement was discussed before KEP creation"

[marosset]

@marosset please provide a Discussion Link. It is required that you "link to SIG mailing list thread, meeting, or recording where the Enhancement was discussed before KEP creation"

Discussed at the SIG-Windows community meetinig on 9/13/2022 - https://youtu.be/gC3lWMtP0-I?t=595

[marosset]

Discussed with SIG-Node at the 9/13/2022 community meeting - meeting notes
Discussed with SIG-Network at the 9/15/2022 community meeting - meeting notes

[kikisdeliveryservice]

Thank you @marosset !!

[rhockenbury]

/label tracked/yes

[parul5sahoo]

Hello @marosset 👋, 1.26 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2022.

This enhancement is targeting for stage alpha for 1.26 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: 1.26
• KEP readme has a updated detailed test plan section filled out
• KEP readme has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

For this KEP, we would just need to update the following:

• Since you might be already aware of the processes yourself not mentioning anything else. 🙂

The status of this enhancement is marked as at risk and will be marked as tracked once the open PR is merged. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[thockin]

Hi, can someone who knows this work fill me in on what's going on?

[MikeZappa87]

@thockin I will sync internally to find out where this is.

[thockin]

This KEP has been open for a long time, but it's not clear if anyone is working on it or planning to. Can we get an update?

[thockin]

One more ping before I close this?

[MikeZappa87]

@thockin sorry for the delay. I thought I had responded back in August but I clearly didn't! This is still in our (Microsoft) queue of work. I am working internally to move this forward.

[thockin]

Any plans here for 1.30?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[MikeZappa87]

/close

[k8s-ci-robot]

@MikeZappa87: Closing this issue.

In response to this:

/close

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-sigs/prow repository.

[sftim]

@MikeZappa87 why close this? It hasn't graduated to stable.

/reopen
I think we should either remove the feature or work towards graduating it.

[k8s-ci-robot]

@sftim: Reopened this issue.

In response to this:

@MikeZappa87 why close this? It hasn't graduated to stable.

/reopen
I think we should either remove the feature or work towards graduating it.

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-sigs/prow repository.

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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-sigs/prow repository.