/k8s_basics/ingress/index.html Generally, Ingress exposes HTTP and HTTPS routes from outside the cluster to services within the cluster. Traffic routing is controlled by rules defined on the Gateway, HTTPRoute and GRPCRoute Resources. The older generation of Kubernetes Ingress uses the Ingress Resource. A Kubernetes Ingress may be configured to give Services externally-reachable URLs, load balance traffic, terminate SSL / TLS, and offer name based virtual hosting, among other things. An Ingress or Gateway Controller is responsible for fulfilling the Ingress, usually with a load balancer, though it may also configure your edge router or additional frontends to help handle the traffic. Hugo en-US /k8s_basics/ingress/nginx/index.html Mon, 01 Jan 0001 00:00:00 +0000 /k8s_basics/ingress/nginx/index.html Setup instructions Stated here just for reference, so don’t execute any of these by yourselves. Besides, so far you haven’t been granted the permissions to do so anyways … :-) Source: [NGINX Ingress Controller Installation Guide][ingress-nginx-quick-start] and thus: helm upgrade --install ingress-nginx ingress-nginx \ --repo https://kubernetes.github.io/ingress-nginx \ --namespace ingress-nginx --create-namespace --version 4.0.17 \ --set controller.admissionWebhooks.enabled=false # disable admissionWebhooks to avoid clashing with Traefik # --set controller.service.externalTrafficPolicy=Local # needed on current AKS For our exercises we now start with ingress-nginx , an Open Source Ingress Controller that is a safe and one of the most popular choices when you need a simple solution. It is maintained and well-integrated by the Kubernetes project itself, with an option for commercial support provided by NGINX Inc, cf. these version differences explained . It has already been set up in our test cluster beforehand (via helm, by the way, see Setup instructions above) so we can jump right at making use of it. /k8s_basics/ingress/traefik/index.html Mon, 01 Jan 0001 00:00:00 +0000 /k8s_basics/ingress/traefik/index.html Setup instructions Stated here just for reference, so don’t execute any of these by yourselves. Besides, so far you haven’t been granted the permissions to do so anyways … :-) Sources: [Install Traefik][install-traefik] [Traefik & Kubernetes: Kubernetes Ingress Controller][traefik-kubernetes-ingress] [Traefik & Kubernetes: Kubernetes Ingress Controller, The Custom Resource Way][traefik-kubernetes-crd] and thus: helm upgrade --install traefik oci://ghcr.io/traefik/helm/traefik \ --namespace traefik --create-namespace --version 38.0.2 \ --set ingressClass.enabled=false \ --set experimental.kubernetesGateway.enabled=true \ --set gateway.enabled=false \ --set providers.kubernetesCRD.ingressClass=traefik \ --set providers.kubernetesIngress.enabled=false \ --set providers.kubernetesGateway.enabled=true \ --set ports.web.redirections.entryPoint.to=websecure \ --set ports.web.redirections.entryPoint.scheme=https \ --set ports.web.redirections.entryPoint.permanent=true Traefik is an open-source Edge Router for publishing services. It receives requests on behalf of your system and finds out which components are responsible for handling them. /k8s_basics/ingress/gatewayapi/index.html Mon, 01 Jan 0001 00:00:00 +0000 /k8s_basics/ingress/gatewayapi/index.html Setup instructions Stated here just for reference, so don’t execute any of these by yourselves. Besides, so far you haven’t been granted the permissions to do so anyways … :-) Source: [Kubernetes Gateway API][k8s-gateway-api] and [Kubernetes Traefik][k8s-traefik] Traefik supports the Kubernetes Gateway API, meaning it can install the Gateway API’s Custom Resource Definitions. As we are running Traefik for some of the exercises, we have already installed the Gateway API CRDs.