KEP-5100: update KEP to stable

[rzlink]

• One-line PR description: Update KEP-5100 state to stable

• Issue link: Support for Direct Service Return (DSR) and overlay networking in Windows kube-proxy  #5100

• Other comments:

[k8s-ci-robot]

Welcome @rzlink!

It looks like this is your first PR to kubernetes/enhancements 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/enhancements has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @rzlink. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[kannon92]

You missed on question here

[marosset]

/ok-to-test

[marosset]

/approve

[soltysh]

Several nits to address

[soltysh]

Later in the document in the GA section you've mentioned:

- 2 or more CNI solutions support overlay networking mode for Windows nodes.

Can you link to those 2 or more CNI solutions supporting it?

[soltysh]

In ###### Are there any tests for feature enablement/disablement? can you link to those tests that you're writing that they will be added?

[marosset]

Calico networking on Windows enables WinOverlay feature if the underlying HNS network is of type overlay
https://github.com/projectcalico/calico/blob/cf9455706a1fc6e9d5b11e4556f3d087007124e7/node/windows-packaging/CalicoWindows/kubernetes/kube-proxy-service.ps1#L65-L79

Flannel does the same
https://github.com/microsoft/SDN/blob/master/Kubernetes/flannel/start-kubeproxy.ps1#L19-L28

We have periodic test passes running in prow that use both of these configurations

• https://testgrid.k8s.io/sig-windows-signal#capz-windows-master-containerd2 (all of the Windows CAPZ tests use calico by default)
• https://testgrid.k8s.io/sig-windows-networking#ltsc2025-containerd-flannel-sdnoverlay-master for flannel with overlay networking mode

[rzlink]

Thanks, @marosset — I’ve updated the PR with the information you provided.

[soltysh]

/approve
the PRR section

[zylxjtu]

/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: marosset, rzlink, soltysh, zylxjtu

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• keps/prod-readiness/OWNERS [soltysh]
• keps/sig-windows/OWNERS [marosset]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment