I brought up an use case for the proxy within Kubernetes. See comment at kubernetes/kubernetes#14226 (comment)
Would it be feasible or even OK to turn the proxy into a library that can run inside either the kube-proxy or kubelet daemons that run on every node in a Kubernetes cluster? My rationale is that it'd be one less daemon to set up/monitor/restart, plus it would allow for better integration. I'll open a separate issue for network=host containers.
I brought up an use case for the proxy within Kubernetes. See comment at kubernetes/kubernetes#14226 (comment)
Would it be feasible or even OK to turn the proxy into a library that can run inside either the kube-proxy or kubelet daemons that run on every node in a Kubernetes cluster? My rationale is that it'd be one less daemon to set up/monitor/restart, plus it would allow for better integration. I'll open a separate issue for network=host containers.