This doc was an attempt to reduce that confusion.
https://kubernetes.io/docs/tasks/access-application-cluster/access-cluster/#so-many-proxies
On Sunday, February 11, 2018 at 9:37:19 PM UTC-8, Tim Hockin wrote:
>
> kube-proxy should be renamed, in truth, but that isn't happening in
> the near ter
kube-proxy should be renamed, in truth, but that isn't happening in
the near term.
On Sun, Feb 11, 2018 at 1:54 PM, Scalefastr wrote:
> kubectl proxy is just for the API server.
>
> But kube-proxy is for services defined in the cluster and available where
> the proxy is running.
>
> I think this
kubectl proxy is just for the API server.
But kube-proxy is for services defined in the cluster and available where
the proxy is running.
I think this is kind of confusing? Is it just me?
Maybe kubectl proxy could/should be renamed to kubectl api-server-proxy
--
You received this message be
