/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 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 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. Cf. this blog post for a general introduction. 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: kubectl create namespace traefik-v2 # let's hardcode the ingress class to avoid potential mixups with other Ingress Controllers, cf. https://docs.traefik.io/providers/kubernetes-ingress/#ingressclass helm upgrade --install --namespace=traefik-v2 traefik traefik --version 10.19.4 \ --repo https://helm.traefik.io/traefik \ --set=ingressClass.enabled=true --set=providers.kubernetesIngress.publishedService.enabled=true \ --set='additionalArguments={--providers.kubernetesingress.ingressclass=traefik,--global.sendanonymoususage=false,--log.level=DEBUG}' 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.