Ingress Controllers

Kubernetes as a project supports and maintains

Additional controllers

• AKS Application Gateway Ingress Controller is an ingress controller that configures the .
• .
• The
• F5 BIG-IP lets you use an Ingress to configure F5 BIG-IP virtual servers.
• , which offers API gateway functionality.
• The is also an ingress controller for
• is an
• The is an ingress controller driving .
• The works with the
• The
• The

You may deploy any number of ingress controllers using ingress class within a cluster. Note the .metadata.name of your ingress class resource. When you create an ingress you would need that name to specify the ingressClassName field on your Ingress object (refer to IngressSpec v1 reference. ingressClassName is a replacement of the older annotation method.

If you do not specify an IngressClass for an Ingress, and your cluster has exactly one IngressClass marked as default, then Kubernetes applies the cluster's default IngressClass to the Ingress. You mark an IngressClass as default by setting the ingressclass.kubernetes.io/is-default-class annotation on that IngressClass, with the string value "true".

Ideally, all ingress controllers should fulfill this specification, but the various ingress controllers operate slightly differently.

What's next

• Learn more about Ingress.
• Set up Ingress on Minikube with the NGINX Controller.