Enabling Ingress Controllers
Explore how to enable and check the status of Ingress controllers in Kubernetes clusters. Understand their role in routing external traffic, handling SSL offloading, and managing requests by path and domain. Gain practical experience with enabling Ingress on k3d and verifying controller health and readiness.
We'll cover the following...
Why are Ingress controllers required?
We need a mechanism that will accept requests on predefined ports (e.g., 80 and 443) and forward them to Kubernetes Services. It should be able to distinguish requests based on paths and domains and be able to perform SSL offloading.
Kubernetes itself does not have a ready-to-go solution for this. Unlike other types of controllers that are typically part of the kube-controller-manager binary, Ingress controllers need to be installed separately. Instead of a controller, kube-controller-manager offers an Ingress resource that other third-party solutions can utilize to provide requests forwarding and SSL features. In other words, Kubernetes only ...