Hacker News new | past | comments | ask | show | jobs | submit login

Why both a ClusterIP and a LoadBalancer services to expose frontend 8080 as 80?

Also, no persistent data storage (no data to the store owner)? (I guess for easier example)




The ClusterIP and LoadBalancer are on separate network interfaces. The ClusterIP exposes the service on an internal interface whereas, the LoadBalancer exposes on a public interface.

https://kubernetes.io/docs/concepts/services-networking/serv...


Hi, the author here! The clusterip one is used by Istio (if you’re following the Istio instructions) but it’s harmless to have an internal LB. The other one is exposing an external LB, which is useful both if you’re using GKE (or any cloud provider) or GKE+Istio.

We deliberately wanted to leave state out as it complicates things by quite a bit, but doesn’t add much value in terms of the technologies we wanted to showcase.


ClusterIP would be to access the frontend from within the cluster. LoadBalancer would of course be for external access.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: