Thanks @PatrickLang I'll add it to the Enhancement tracking sheet. Just a reminder, the KEP must be merged, in an implementable state with a test plan and graduation criteria defined by EoD tomorrow at 5pm PT.

/milestone v1.17

@PatrickLang Thanks for going ahead and filing an exception request, we'll follow up there for review 👍

For now it's being removed from the milestone and flagged as tracked/no. If approved it'll be added back in.

@guineveresaenger approved the exception, so I am adding this back to the 1.17 milestone.

/milestone v1.17

Hello, @PatrickLang I'm 1.17 docs lead.

Does this enhancement (or the work planned for v1.17) require any new docs (or modifications to existing docs)? If not, can you please update the 1.17 Enhancement Tracker Sheet (or let me know and I'll do so)

If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.17) due by Friday, November 8th, it can just be a placeholder PR at this time. Let me know if you have any questions!

Hello, @PatrickLang

Please let us know if this enhancement requires docs. If so, We're hoping to have a placeholder Docs PR against k/website (branch dev-1.17) by Friday, Nov 8th. (4 more days left)

Hi @PatrickLang

I am one of the Enhancements Shadow for the 1.17 Release Team. We are very near to the Code Freeze (Nov 14th) for this release cycle. Just checking in about the progress of this enhancement. Can you please link the PR's related to this enhancement here?

Thank you in advance 😄

Hello @PatrickLang

Just a friendly reminder, We're hoping to have a placeholder Docs PR against k/website (branch dev-1.17) by Friday, Nov 8th. (2 more days left)

@palnabarun @daminisatya @jeremyrickard - PRs attached. There may be additional code PRs as the current one is a WIP and under active discussion and review with SIG-Node before proceeding with the next steps.

@PatrickLang Thank you for the updates 😀

Hi @PatrickLang , tomorrow is code freeze for the 1.17 release cycle. It looks like the k/k PRs have not yet been merged. We're flagging as the enhancement as At Risk in the 1.17 Enhancement Tracking Sheet.

Do you think they will be merged by the EoD of the 14th (Thursday)? After that point, only release-blocking issues and PRs will be allowed in the milestone with an exception.

/assign @PatrickLang

This has one of the use cases complete and merged. I will update the doc bug tomorrow for that. The other use case related to multiple OS versions on the same node will be moved out.

How do you want to track this? Keep this open and move to 1.18?

/stage alpha

/milestone v1.19

Hello, @PatrickLang ! 👋 I'm one of the v1.19 Docs shadows. Does this enhancement work planned for v1.19 require any new docs (or modifications to existing docs)?

I saw that this docs PR was merged kubernetes/website#16697 a couple of months ago.

Regards,
Mikael.

@marosset -- As per our conversation on Slack, I have updated the tracking sheet. Thanks for the pro-active ping. 👍

/milestone clear

Thanks @palnabarun!
Unfortunately I don't think we'll be finished with the work for this to go to alpha for 1.19.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

Hi @PatrickLang @marosset

Enhancements Lead here, do you still intend to go alpha in 1.20?

Thanks!
Kirsten

@kikisdeliveryservice I'm starting a discussion with SIG-Windows leads about this now.

Sounds good, please keep us updated!

Hi @kikisdeliveryservice - I spoke with sig-windows leads and since we don't foresee needing any implementation PRs in k/k we didn't think tracking this as an enhancement makes sense.
Pretty much all of the remaining work here is making sure there is adequate test coverage in periodic jobs on testgrid as well as documentation.
Should I close this issue for now and re-open if the situation changes?

@marosset that sounds good to me!

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@fejta-bot: Closing this issue.