AFAIK, the VMWare cloud provider doesn't support LoadBalancer.
On Monday, August 21, 2017 at 7:04:17 PM UTC+2, Snd LP wrote:
>
> Baremetal/VMware.
>
> Does "," look normal before "EXTERNAL-IP" ?
> Thanks.
>
> [root@kctl-master kubectl]# kubectl get services
> NAMECLUSTER-IP EXTERN
Baremetal/VMware.
Does "," look normal before "EXTERNAL-IP" ?
Thanks.
[root@kctl-master kubectl]# kubectl get services
NAMECLUSTER-IP EXTERNAL-IP PORT(S)AGE
kubernetes 10.254.0.1 443/TCP4d
nginx-ingress 10.254.86.23 ,172.23.162.232
I meant what does your cluster run on? E.g AWS, bare metal. The Kubernetes
documentation refers to this as the "cloud provider". Not all cloud
providers support the LoadBalancer type. See this article [1] for a nice
overview of how to access pods externally.
[1]
http://alesnosek.com/blog/2017/
1 master, 3 nodes.
3 interfaces each.
what is the most common setup?
On Sat, Aug 19, 2017 at 2:31 AM, Rémon Sinnema wrote:
> How did you set up your cluster? The LoadBalancer type is not supported
> everywhere, e.g. when using kubeadm.
>
> On Wednesday, August 16, 2017 at 11:08:39 PM UTC+2, Sn
How did you set up your cluster? The LoadBalancer type is not supported
everywhere, e.g. when using kubeadm.
On Wednesday, August 16, 2017 at 11:08:39 PM UTC+2, Snd LP wrote:
>
> [ansible@kctl-master kubectl]$ sudo kubectl get services
> NAMECLUSTER-IP EXTERNAL-IP PORT(S)
