Hi William, So here is what I tried
This is my service config.yaml *apiVersion: v1* *kind: Service* *metadata:* * name: echo-server* *spec:* * ports:* * - port: 11111* * nodePort: 30080* * name: "echo-server"* * selector:* * app: echo-server* * clusterIP: None* * type: NodePort* and then I did *kubectl describe node *to get the external IP of the machine (as I want clients who are external to the cluster should be able to connect) where "echo-server" pod is running and finally did telnet <externalIP> 30080 // This didn't quite work. any idea? On Tue, Jun 21, 2016 at 1:35 PM, kant kodali <[email protected]> wrote: > Thanks! I assume you meant IP:Nodeport. > > On Tue, Jun 21, 2016 at 12:14 PM, Warren Strange <[email protected] > > wrote: > >> >> NodePorts are exposed on every node in the cluster. If you node has an >> externally reachable IP, you can reach your service through nodeport:IP >> >> >> >> On Tuesday, June 21, 2016 at 1:04:15 PM UTC-6, kant kodali wrote: >>> >>> Hi Warren, >>> >>> I want my headless service to be visible by the clients external to the >>> cluster but I am not sure how? (I understand through NodePorts it is >>> accessible within the cluster) . The clients who are external to the >>> cluster will do the load balancing themselves. >>> >>> Thanks, >>> Kant >>> >>> On Sun, Jun 19, 2016 at 1:14 PM, Warren Strange <[email protected]> >>> wrote: >>> >>>> >>>> You can expose your service through a NodePort - which will be >>>> available on all nodes in the cluster. You need to open up the relevant >>>> firewall ports. >>>> >>>> If you want to do your own load balancing see: >>>> >>>> https://blog.oestrich.org/2016/01/nodeport-kubernetes-load-balancer/ >>>> >>>> >>>> >>>> On Sun, Jun 19, 2016 at 1:38 PM kant kodali <[email protected]> wrote: >>>> >>>>> HI Warren, >>>>> >>>>> Yes I want my headless service to be internet accessible. Also our >>>>> requirement is that we dont want to attach a load balancer because we dont >>>>> want to go through the kube-proxy instead we want to do the load balancing >>>>> ourselves. is this a possibility with kubernetes? >>>>> >>>>> Thanks, >>>>> Kant >>>>> >>>>> On Sun, Jun 19, 2016 at 10:47 AM, Warren Strange <[email protected] >>>>> > wrote: >>>>> >>>>>> >>>>>> If you just want to talk to a service from your desktop, you can >>>>>> often use kubectl proxy, or kubectl port-forward to forward local >>>>>> traffic >>>>>> to the cluster. >>>>>> >>>>>> If you want a real DNS name, and your service to be internet >>>>>> accessible, you need to setup an ingress resource. >>>>>> >>>>>> >>>>>> >>>>>> On Saturday, June 18, 2016 at 3:17:19 PM UTC-6, kant kodali wrote: >>>>>>> >>>>>>> Hi Guys, >>>>>>> >>>>>>> Is there a way to get a public DNS or something of a headless >>>>>>> service inside my kubernetes cluster so that I can talk to the pods >>>>>>> backed >>>>>>> by my headless service from my home computer per say? >>>>>>> >>>>>>> Thanks! >>>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to a topic in >>>>>> the Google Groups "Containers at Google" group. >>>>>> To unsubscribe from this topic, visit >>>>>> https://groups.google.com/d/topic/google-containers/rRKvj4-uPdI/unsubscribe >>>>>> . >>>>>> To unsubscribe from this group and all its topics, send an email to >>>>>> [email protected]. >>>>>> To post to this group, send email to [email protected]. >>>>>> Visit this group at https://groups.google.com/group/google-containers >>>>>> . >>>>>> 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 "Containers at Google" group. >>>>> To unsubscribe from this topic, visit >>>>> https://groups.google.com/d/topic/google-containers/rRKvj4-uPdI/unsubscribe >>>>> . >>>>> To unsubscribe from this group and all its topics, send an email to >>>>> [email protected]. >>>>> To post to this group, send email to [email protected]. >>>>> Visit this group at https://groups.google.com/group/google-containers. >>>>> 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 "Containers at Google" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/google-containers/rRKvj4-uPdI/unsubscribe >>>> . >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> To post to this group, send email to [email protected]. >>>> Visit this group at https://groups.google.com/group/google-containers. >>>> 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 "Containers at Google" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/google-containers/rRKvj4-uPdI/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at https://groups.google.com/group/google-containers. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Containers at Google" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-containers. For more options, visit https://groups.google.com/d/optout.
