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

/sig node network
/label lead-opted-in

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

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

Thank you @marosset !!

/label tracked/yes

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!

Candidate for Alpha in 1.26 ?

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.

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

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

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

Thanks!

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!

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:

• Windows hostnetwork alpha kubernetes#112961

As always, we are here to help should questions come up. Thanks!

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

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

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

/remove-lifecycle stale

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

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

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?

One more ping before I close this?

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

Any plans here for 1.30?

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