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
I'm setting up a kubernetes clusters via "the hard way" but I"m stuck.
Right now I'm using flannel (tried canal too) and the apiserver runs with a
'kubernetes' cert.
I get this when I run kubectl:
root@host-9c16fd7a ~ # kubectl logs busybox-855686df5d-ln6ww
Error from server (Forbidden):
It's 2018... I'm really surprised that Docker and Kubernetes are still
dragging their feet with IPv6 support.
Shouldn't we be putting IPv6 support *first*?
For example, Docker has it disabled by default.
I really subscribe to the mobile first and H2 first movements. Prioritize
and reward
