Course contentsShow
← Cloud and Infrastructure
Lesson 1219 of 2,98924. Kubernetes NetworkingFree lesson

Ingress Resource Fundamentals

Understand the Ingress API object and how it defines HTTP/HTTPS routing rules for external access to cluster services.

Ingress Resource Fundamentals

What you'll learn: How Kubernetes uses Ingress resources to route external HTTP/HTTPS traffic to services inside your cluster using domain names and paths.

What Is an Ingress?

An Ingress is a Kubernetes API object that defines rules for routing external HTTP and HTTPS traffic to your cluster's Services. Think of it as a sophisticated receptionist at a large office building: when visitors (HTTP requests) arrive asking for specific departments (services), the Ingress knows exactly where to direct them based on which door they used (domain name) or which floor they're looking for (URL path).

Without Ingress, you'd need a separate LoadBalancer Service for each application you want to expose externally—expensive and complex. Ingress consolidates this, letting multiple services share a single external IP address.

How Ingress Works

The Ingress resource itself is just a configuration—a set of routing rules you define in YAML. It specifies:

  • Host-based routing: api.myapp.com → Service A, web.myapp.com → Service B
  • Path-based routing: myapp.com/api → Service A, myapp.com/admin → Service B
  • Backend services: Which ClusterIP Services receive the traffic
  • TLS/SSL configuration: Certificates for HTTPS termination

The actual traffic routing is handled by an Ingress Controller (a separate component you must install), but understanding the Ingress resource itself is the first step.

The Relationship to Services

Ingress sits in front of your Services (typically ClusterIP type). External traffic hits the Ingress Controller, which reads your Ingress rules and forwards requests to the appropriate Service, which then load-balances to healthy Pods using Endpoints/EndpointSlices—concepts you already know.

Key Takeaway: The Ingress resource is a declarative configuration that defines HTTP/HTTPS routing rules, enabling smart, path- and host-based traffic distribution to multiple backend Services through a single entry point.