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...

In Kubernetes, an endpoint refers to the set of network addresses (IP addresses and ports) that are associated with a Kubernetes service. Endpoints are used to keep track of the Pods that are dynamically assigned to a service. Here's a more detailed breakdown of what endpoints are and how they work: Key Concepts: Services : A Kubernetes Service is an abstraction that defines a logical set of Pods and a policy by which to access them. Services enable network access to a group of Pods in a Kubernetes cluster. Services can be exposed internally within the cluster (ClusterIP), externally to the internet (LoadBalancer or NodePort), or can be headless (without a stable IP address). Pods : Pods are the smallest and simplest Kubernetes objects. A Pod represents a single instance of a running process in your cluster. Pods are ephemeral, meaning they can be created and destroyed dynamically. Endpoints : Endpoints in Kubernetes are the objects that associate a service with the actual Pod IP ...