4 ms·
I should note the title of the article should be "L7 Routing" not "L7" (obviously)
by TheIronYuppie 11y ago
I should note the title of the article should be "L7 Routing" not "L7" (obviously)
- HorizonXP 11y agoI have definitely been waiting for this for a long time! I read through the tutorial, but haven't had a chance to implement it. Two questions: 1) I run some services on DigitalOcean. Does this mean I can run a Kubernetes cluster, designate my controller as my Ingress, point my DNS entry there and it will load-balance? 2) is this a different type of load balancer type in the Service definition? This could be helpful and useful on my ESXi clusters too.
- truthninja 11y ago> 1) I run some services on DigitalOcean. Does this mean I can run a Kubernetes cluster, designate my controller as my Ingress, point my DNS entry there and it will load-balance? Yeah, you'd need to deploy the nginx controller. Or the service-loadbalancer, which doesn't yet handle Ingress but conceptually does the same loadbalancing at L7 with plain Kubernetes Services. Both these can be found at: https://github.com/kubernetes/contrib https://github.com/kubernetes/contrib >2) is this a different type of load balancer type in the Service definition? No, the community is debating moving L4 loadbalancing out of Services and keeping Services to mean "Backend services". Ingress spans services and encapsulates higher level concepts that require more context (eg: use a single IP to loadbalance entire cluster based on hostname vs type=loadbalancer which allocates an LB per service, SNI, atomic updates to a single URL map for blue/green deployment etc).