You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Sounds ok to me, although I personally think it would be better to run it as a separate daemon. It would just take some shuffling of the code, I think.
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.
The text was updated successfully, but these errors were encountered: