3 ms·
We're running many small (10s of nodes) clusters on metal with coreos. Networking is some in house stuff we've purpose built so we can get public ips on the pod
by nethier 10y ago
We're running many small (10s of nodes) clusters on metal with coreos. Networking is some in house stuff we've purpose built so we can get public ips on the pod.
Internal adoption seems to be going well so hopefully this grows.
- leetbulb 10y agoCheck out the new Ingress stuff for exposing services to public. http://kubernetes.io/docs/user-guide/ingress/ http://kubernetes.io/docs/user-guide/ingress/ https://github.com/kubernetes/contrib/tree/master/ingress/controllers/nginx https://github.com/kubernetes/contrib/tree/master/ingress/co... The ingress controller runs on nodes with a public IP. When you create an ingress for one of your services, one of the controllers will pick that up and expose it. The ingress controller linked above is built on nginx and essentially just reconfigures nginx based on your ingress resource spec. Similar to when you define a LoadBalancer in a service with GCE, the service's external IP is set to the upstream ingress controller node's public IP.