Ingress
Ingress is a powerful kubernetes API object that manages external access to the cluster. The Ingress concept lets you map traffic to different backends based on rules you define via the Kubernetes API. It may provide load balancing, SSL/TLS termination with certificates for HTTPS access.
Ingress is often used to expose multiple services under the same IP adress and supports advanced capabilities such as:
- path based routing (eg. /api to service)
- host based routing( eg. www.ingress.com)
- integration with external authentification and rate limiting policies.
In a production environment, Ingress is a fundamental component for managing traffic, security, scalability and observability at the edge of a kubernetes cluster.
Related articles
Notes after Katacoda Training on Kubernetes Container Orchestration
Categories: Containers Orchestration, Learning | Tags: Helm, Kubeadm, CNI, Micro Services, Minikube, Ingress, Kubernetes
A few weeks ago, I dedicated two days to follow the turorials available on Katacoda, the interactive learning platform for Kubernetes or any other container orchestration platform. I’m sharing my…
By David WORMS
Dec 14, 2017
Ingresses and Load Balancers in Kubernetes with MetalLB and nginx-ingress
Categories: Containers Orchestration, Infrastructure, Tech Radar | Tags: Kubeadm, Cluster, Deployment, Ingress, Kubernetes
When it comes to exposing services from a Kubernetes cluster and making it accessible from outside the cluster, the recommended option is to use a load-balancer type service to redirect incoming…
Sep 8, 2022
