Skip to content
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

Host network support for Windows pods #3503

Open
4 tasks done
marosset opened this issue Sep 12, 2022 · 26 comments
Open
4 tasks done

Host network support for Windows pods #3503

marosset opened this issue Sep 12, 2022 · 26 comments
Assignees
Labels
sig/network Categorizes an issue or PR as relevant to SIG Network. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/windows Categorizes an issue or PR as relevant to SIG Windows. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status

Comments

@marosset
Copy link
Contributor

marosset commented Sep 12, 2022

Enhancement Description

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

@k8s-ci-robot
Copy link
Contributor

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

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Sep 12, 2022
@marosset marosset added sig/windows Categorizes an issue or PR as relevant to SIG Windows. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Sep 12, 2022
@marosset
Copy link
Contributor Author

/sig node network
/label lead-opted-in

@k8s-ci-robot k8s-ci-robot added sig/node Categorizes an issue or PR as relevant to SIG Node. sig/network Categorizes an issue or PR as relevant to SIG Network. lead-opted-in Denotes that an issue has been opted in to a release labels Sep 13, 2022
@marosset marosset added this to the v1.26 milestone Sep 13, 2022
@kikisdeliveryservice
Copy link
Member

@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
Copy link
Contributor Author

@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
Copy link
Contributor Author

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
Copy link
Member

Thank you @marosset !!

@rhockenbury
Copy link

/label tracked/yes

@k8s-ci-robot k8s-ci-robot added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Sep 20, 2022
@rhockenbury rhockenbury added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Sep 20, 2022
@parul5sahoo
Copy link

parul5sahoo commented Sep 22, 2022

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 thockin moved this from New, not evaluated to Evaluated, not committed (undecided whether we want to do this or not) in Obsolete: SIG-Network KEPs (see https://github.com/orgs/kubernetes/projects/148) Sep 29, 2022
@thockin
Copy link
Member

thockin commented Sep 29, 2022

Candidate for Alpha in 1.26 ?

@marosset
Copy link
Contributor Author

Candidate for Alpha in 1.26 ?

Yes - work is needed in the container runtimes (just containerd for Windows) so the sooner we get the CRI-API changes in the sooner we can move towards beta/stable.

@rhockenbury
Copy link

Hello 👋, 1.26 Enhancements Lead here.

Unfortunately, this enhancement did not meet requirements for enhancements freeze.

If you still wish to progress this enhancement in v1.26, please file an exception request. Thanks!

/milestone clear
/label tracked/no
/remove-label tracked/yes
/remove-label lead-opted-in

@k8s-ci-robot k8s-ci-robot added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Oct 7, 2022
@k8s-ci-robot k8s-ci-robot removed this from the v1.26 milestone Oct 7, 2022
@k8s-ci-robot k8s-ci-robot removed the lead-opted-in Denotes that an issue has been opted in to a release label Oct 7, 2022
@marosset
Copy link
Contributor Author

marosset commented Oct 7, 2022

@rhockenbury - #3507 merged before the enahcnement freeze. Is there a reason why this didn't make it into v1.26?

@rhockenbury
Copy link

My mistake. I missed that there was a PR merged up for this. This is tracked for v1.26

/milestone v1.25
/label tracked/yes
/lead-opted-in
/remove-label tracked/no

@k8s-ci-robot k8s-ci-robot added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Oct 7, 2022
@k8s-ci-robot k8s-ci-robot added this to the v1.25 milestone Oct 7, 2022
@rhockenbury rhockenbury added the lead-opted-in Denotes that an issue has been opted in to a release label Oct 7, 2022
@marosset
Copy link
Contributor Author

marosset commented Oct 7, 2022

Thanks!

@cathchu
Copy link

cathchu commented Nov 2, 2022

Hello @marosset 👋 1.26 Release Docs shadow 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 dev-1.26 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by November 9. Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thank you!

@marosset
Copy link
Contributor Author

marosset commented Nov 7, 2022

Hi @marosest 👋,

Checking in once more as we approach 1.26 code freeze at 17:00 PDT on Tuesday 8th November 2022.

Please ensure the following items are completed:

  • All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
  • All PRs are fully merged by the code freeze deadline.

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!

@marosset
Copy link
Contributor Author

marosset commented Nov 8, 2022

All of the code PRs have merged so I'm marking this enhancement as Tracked for v1.26.

@marosset
Copy link
Contributor Author

/remove-label lead-opted-in
/remove-label tracked/yes
/label tracked/no
/milestone clear

@k8s-ci-robot k8s-ci-robot added the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label Dec 14, 2022
@k8s-ci-robot k8s-ci-robot removed this from the v1.26 milestone Dec 14, 2022
@k8s-ci-robot k8s-ci-robot removed lead-opted-in Denotes that an issue has been opted in to a release tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Dec 14, 2022
@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 14, 2023
@marosset
Copy link
Contributor Author

marosset commented Apr 6, 2023

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 6, 2023
@Atharva-Shinde Atharva-Shinde removed the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label May 14, 2023
@thockin
Copy link
Member

thockin commented Jun 8, 2023

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

@MikeZappa87
Copy link

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

@thockin
Copy link
Member

thockin commented Aug 17, 2023

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
Copy link
Member

thockin commented Sep 27, 2023

One more ping before I close this?

@MikeZappa87
Copy link

@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
Copy link
Member

thockin commented Jan 18, 2024

Any plans here for 1.30?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/network Categorizes an issue or PR as relevant to SIG Network. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/windows Categorizes an issue or PR as relevant to SIG Windows. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status
Projects
Status: Net New
Obsolete: SIG-Network KEPs (see https...
Evaluated, not committed (undecided w...
Status: In Progress
Development

No branches or pull requests

10 participants