Description of the feature you would like to add / User story
As a user
I would like to be free of choice of my CNI and if I want to use kubeProxy or not
in order to customize my stack and integrate in an easy way e.g. Cilium EE over an Application.
Solution details
If I select cilium as overlay I have the option iptables and ebpf. ebpf is more or less disabling the deployment of the kubeproxy what is nice as Cilium can take this function over without overhead of the kubeporxy daemon set.
If I select the CNI Type None I would like to configure the KubeProxy mode ebpf as well to rollout e.g. Cilium EE over Applications. There this Option is not given.
Alternative approaches
Right now using iptables mode and live with the kubeproxy.
Use cases
Integrate any KubeNative CNIs what may need or need not kubeproxy.
Description of the feature you would like to add / User story
As a user I would like to be free of choice of my CNI and if I want to use kubeProxy or not in order to customize my stack and integrate in an easy way e.g. Cilium EE over an Application.
Solution details
If I select cilium as overlay I have the option
iptables
andebpf
.ebpf
is more or less disabling the deployment of the kubeproxy what is nice as Cilium can take this function over without overhead of the kubeporxy daemon set.If I select the CNI Type
None
I would like to configure the KubeProxy modeebpf
as well to rollout e.g. Cilium EE over Applications. There this Option is not given.Alternative approaches
Right now using iptables mode and live with the kubeproxy.
Use cases
Integrate any KubeNative CNIs what may need or need not kubeproxy.
Additional information