Thread by @TheNJDevOpsGuy

Are you using Ingress Controllers in your Kubernetes environment?

If not, let's break down what they are.

A thread 🧵

At a high level, Ingress Controllers are:
- Specify multiple paths
- Specify multiple services

All in one load balancer.

Let's break it down.

ingress Controllers are just like any other Controller in a Kubernetes environment. They confirm that the current state is the desired state for the deployment.

You can create one load balancer and have every Kubernetes Service point to it. Then, you can access each Kubernetes Service on a different path.

This is beneficial from a management perspective so engineers don't have to manage multiple load balancers and from a cost perspective. Cloud load balancers cost money.

An Ingress Controller is a load balancer and a proxy within itself. It routes traffic to the Service, and then the Service routes traffic to Pods.

The thing is, you still have to manage an Ingress Controller. From overall deployment to management with `kubectl`.

Check out how to make this easier at the link below.

www-portainer-io.cdn.ampproject.org/c/s/www.portai…

#kubernetes #devops #docker