Ingress-nginx: difference between service-loadbalancer and ingress

[jwfang]

seems service-loadbalancer
https://github.com/kubernetes/contrib/tree/master/service-loadbalancer
accomplish the same functions as ingress, except there are much more implementation for ingress.

1. what's the difference ?
2. which one should i choose ?

[rikatz]

@jwfang service-loadbalancer has been discontinued as Ingress is the official method of configuring ingresses.

The main difference is that Ingress is supported by an official object inside Kubernetes API, although service-loadbalancer only uses a 'Service' object, and this may leed to some confusion.

Basically Ingress Controller does the same: Reads the Kubernetes API to check the Ingress Objects (and related secrets, used as TLS Certificates) and reconfigures the chosen WebServer to act as a proxy between the real world and the Container World.

This implementation uses NGINX (or Google GCE LB), but there are some other implementations using HAProxy, as an example.

You should use Ingress, as SLB has been deprecated.

If this answer is applicable for you, please close this issue :)

[aledbf]

@jwfang service-loadbalancer predates Ingress and do not allows a granular configuration and all the services in the cluster are published.
Please reopen if you have more questions

[jwfang]

sorry for the late, thank you guys.