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 > NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE > kubernetes 10.254.0.1 <none> 443/TCP 4d > nginx-ingress 10.254.86.23 ,172.23.162.232 80:32102/TCP 2m > [root@kctl-master kubectl]# cat 0-ingress.yaml > apiVersion: v1 > kind: Service > metadata: > name: nginx-ingress > spec: > type: LoadBalancer > ports: > - port: 80 > name: http > nodePort: 32102 > protocol: TCP > selector: > k8s-app: nginx-ingress-lb > externalIPs: > - 172.23.162.232 > > [root@kctl-master kubectl]# > > On Sun, Aug 20, 2017 at 1:52 AM, Rémon Sinnema <rsin...@gmail.com > <javascript:>> wrote: > >> 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/02/14/accessing-kubernetes-pods-from-outside-of-the-cluster/ >> >> >> On Saturday, August 19, 2017 at 2:01:03 PM UTC+2, Snd LP wrote: >>> >>> 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 <rsin...@gmail.com> >>> 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, Snd LP wrote: >>>>> >>>>> [ansible@kctl-master kubectl]$ sudo kubectl get services >>>>> NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE >>>>> kubernetes 10.254.0.1 <none> 443/TCP 43s >>>>> nginx-ingress 10.254.39.207 <pending> 80:32102/TCP 1m >>>>> [ansible@kctl-master kubectl]$ >>>>> >>>>> after running, >>>>> >>>>> trying to have a virtual-ip not being used by this or any nodes for HA. >>>>> >>>>> [ansible@kctl-master kubectl]$ cat 0-ingress.yaml >>>>> apiVersion: v1 >>>>> kind: Service >>>>> metadata: >>>>> name: nginx-ingress >>>>> spec: >>>>> type: LoadBalancer >>>>> ports: >>>>> - port: 80 >>>>> name: http >>>>> nodePort: 32102 >>>>> selector: >>>>> k8s-app: nginx-ingress-lb >>>>> [ansible@kctl-master kubectl]$ >>>>> >>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "Kubernetes user discussion and Q&A" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/kubernetes-users/VuWzjnf-G9w/unsubscribe >>>> . >>>> To unsubscribe from this group and all its topics, send an email to >>>> kubernetes-use...@googlegroups.com. >>>> To post to this group, send email to kubernet...@googlegroups.com. >>>> Visit this group at https://groups.google.com/group/kubernetes-users. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Kubernetes user discussion and Q&A" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/kubernetes-users/VuWzjnf-G9w/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> kubernetes-use...@googlegroups.com <javascript:>. >> To post to this group, send email to kubernet...@googlegroups.com >> <javascript:>. >> Visit this group at https://groups.google.com/group/kubernetes-users. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
