https://k8s-school.fr/labs/k8s/en/tags/ingress/index.htmlHugoenCopyright (c) 2025 Fabrice Jammes - Licensed under CC BY-SA 4.0Mon, 15 Jun 2026 14:15:26 +1000https://k8s-school.fr/labs/k8s/en/1_labs/openshift-ingress-route/index.htmlMon, 15 Jun 2026 14:15:26 +1000https://k8s-school.fr/labs/k8s/en/1_labs/openshift-ingress-route/index.htmlAuthor: Fabrice JAMMES (LinkedIn). Duration: 20-30 minutes Objective OpenShift predates the Kubernetes Ingress API by several years. Its native object for exposing HTTP(S) services is the Route (route.openshift.io/v1), handled by the HAProxy-based router. To stay compatible with portable Kubernetes manifests, OpenShift ships a controller — part of openshift-controller-manager / route-controller-manager — that watches every Ingress object cluster-wide and automatically creates a matching Route for it.