If you watched my previous video on Kubernetes Services then you already know a variety of ways you can access Kubernetes Services from outside the cluster. Kubernetes Ingress adds another option, building on top of the base primitives of Kubernetes Services, to provide application layer load balancing for HTTP/HTTPS based services. But exactly what you get and how it works depends on which specific Ingress Controller you are using – and there are a lot of choices!
This short video explains the basic differences and how these translate to real networking behavior.
In the video you’ll learn:
- How basic in-cluster ingress load balancers can provide access to services from outside the cluster.
- How external application load balancers can be used as an alternative to in-cluster load balancers.
- The different service routing modes supported by application load balancers.
- The pros and cons of each of the above, to help you understand why you might choose one vs another, depending on your needs and specific cluster environment.
If you enjoyed this video then you may also like:
- Everything you need to know about Kubernetes Services networking
- Everything you need to know about Kubernetes networking on AWS
- Everything you need to know about Kubernetes networking on Azure
- Everything you need to know about Kubernetes networking on Google Cloud
- Free online training at projectcalico.org/events or subscribe to Calico Essentials for personalized training & workshops