kube-router: Kube-router shouldn't rely on kube-proxy configmap

Hi, this PR https://github.com/kubernetes/kubernetes/pull/89593 introduces the important change to provide seamless an upgrade for a cluster using kubeadm and without risks having kube-proxy installed again, but it is rely on missing kube-proxy config.

Problem is that kube-router deployed as service-proxy rely on this kube-proxy config:

https://github.com/cloudnativelabs/kube-router/blob/5c5dc411232495f11f6292fb9e4168ae6e228047/daemonset/kubeadm-kuberouter-all-features.yaml#L53-L57 https://github.com/cloudnativelabs/kube-router/blob/5c5dc411232495f11f6292fb9e4168ae6e228047/daemonset/kubeadm-kuberouter-all-features.yaml#L83-L84 https://github.com/cloudnativelabs/kube-router/blob/5c5dc411232495f11f6292fb9e4168ae6e228047/daemonset/kubeadm-kuberouter-all-features.yaml#L127-L132

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 2
Comments: 17 (9 by maintainers)

Most upvoted comments

I personally don’t find using the kubelet’s config any better practice than using kube-proxy’s, but I can see how not using a component that kube-router has the potential to replace helpful to some use-cases. So I’d be willing to review / test / merge if someone wants to go through the effort of putting up a PR.

The difference is that kubernetes can work without kubeadm and kube-proxy. But it can not work without the kubelet. And the kubelet will always need to connect to the API server without a cluster-ip. So it will always have the information that kube-router needs.

asteven on Aug 16, 2021