kubernetes
WIP: KEP-5343: Updates to kube-proxy-backends
- One-line PR description: Post-KEP-3866, figure out what to do about "default" kube-proxy backend and deprecated backends
- Issue link: https://github.com/kubernetes/enhancements/issues/5343
(This is WIP, but ready for review; the WIP-iness is about figuring out the scope/details of what we want to do.)
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: danwinship
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~keps/sig-network/OWNERS~~ [danwinship]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
a good exercise for people willing to help will be to create a standalone repo with the ipvs proxy and windows proxy from the existing code in k/k to show feasibility ... I think that if that works we just start the deprecation period and point the people that wants to use them to this new repo ...
a good exercise for people willing to help will be to create a standalone repo with the ipvs proxy and windows proxy from the existing code in k/k to show feasibility ... I think that if that works we just start the deprecation period and point the people that wants to use them to this new repo ...
Just wondering whether the approach has been finalized. Will it be a separate repository within the Kubernetes project, for example: kubernetes/kube-proxy-windows?
Thanks,
I see that https://github.com/kubernetes/enhancements/issues/5343 is on the 1.35 enhancement board but I'm not sure if this KEP is ready for 1.35?
Should we remove this from the milestone?
