Formation DevOps Jour 29: Kubernetes Ingress | Exposer Plusieurs Apps sur un Seul Domaine Pro !

The twenty-ninth session of a DevOps training series focuses on Kubernetes Ingress functionality. This theoretical session details how to expose multiple web applications, such as frontends, APIs, or administrative interfaces, through a single domain and entry point within a Kubernetes cluster. It addresses the limitations of relying solely on Kubernetes Services for external exposure, particularly concerning cost and complexity associated with managing numerous LoadBalancers.

The core content explains the concept of Kubernetes Ingress, outlining its role as an intelligent HTTP router. The presentation distinguishes between the Ingress resource definition and the necessity of an Ingress Controller, which facilitates the actual traffic management. The internal operation flow is described: external traffic moves from the LoadBalancer to the Ingress Controller, which then routes requests to the appropriate internal Kubernetes Services based on predefined rules.

Furthermore, the video covers advanced routing capabilities offered by Ingress, including path-based routing (e.g., distinguishing traffic for /api versus /web) and potentially subdomain routing. This mechanism enables efficient traffic management and the implementation of secure communication protocols like HTTPS without requiring a dedicated external IP address per application.