Hi guys, I was wondering if there is another way to route external traffic to a Pod. So I know that you can use a Kubernetes Service of type "LoadBalancer" which on GKE will automatically create a Google Cloud Loadbalancer for you (as described here https://kubernetes.io/docs/concepts/services-networking/service/#type-loadbalancer). However having a Google Cloud Loadbalancer is complete overkill for my small use case and also relatively expensive.
Furthermore I've seen solutions online, where people would use externalIPs on the service and then used the external IP of the Node itself to access the Pod (see for example here https://serverfault.com/questions/801189/expose-port-80-and-443-on-google-container-engine-without-load-balancer). However since your container can be assigned to any Node, this solution is not really suitable as with each new deployment you have to look up the IP current Node. Isn't there a way, to just reserve an external IP via Google Cloud and then "attach" a Kubernetes Service to it? -- 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.
