DevOps KB Pages

Kubernetes Ingress and Service LoadBalancer both handle external access to applications running in a Kubernetes cluster, but they operate in different ways and are used in different scenarios. Here’s a comparison to understand their differences: Kubernetes Service LoadBalancer Purpose : Exposes a single Service to external traffic by creating a load balancer. Operation : Directly creates a cloud provider load balancer (e.g., AWS ELB, GCP LB). Maps a single Service to the external load balancer, which routes traffic to the Service's Pods. Provides a single external IP address for the Service. Use Case : Suitable for simple use cases where a single Service needs to be exposed to external traffic. Complexity : Less complex setup, easy to configure, ideal for straightforward scenarios. Example : Exposing a single web application to the internet. Kubernetes Ingress Purpose : Manages external access to multiple Services, typically HTTP and HTTPS, providing load balancing, SSL termination...

 Ingress has two components: - Ingress Controller      The controller is deployed as a pod on all the nodes (i.e. Nginx)     The pods are deployed using a "Deployment"     the default route is defined in the deployment     there is NO "kind: IngressController" there is only kind "ingress" after the controller has been deployed in the cluster. - Ingress Resource     The resources is used to route the traffic to the correct backend/service References: https://overcast.blog/kubernetes-ingress-controllers-and-ingress-resources-a-practical-guide-7a709dec3e4b