Edit This Page

Ingress Controllers

In order for the Ingress resource to work, the cluster must have an ingress controller running.

Unlike other types of controllers which run as part of the kube-controller-manager binary, Ingress controllers are not started automatically with a cluster. Use this page to choose the ingress controller implementation that best fits your cluster.

Kubernetes as a project currently supports and maintains GCE and nginx controllers.

• Additional controllers
• Using multiple Ingress controllers
• What's next

Additional controllers

• Ambassador API Gateway is an Envoy based ingress controller with community or commercial support from Datawire.
• AppsCode Inc. offers support and maintenance for the most widely used HAProxy based ingress controller Voyager.
  
• Contour is an Envoy based ingress controller provided and supported by Heptio.
• Citrix provides an Ingress Controller for its hardware (MPX), virtualized (VPX) and free containerized (CPX) ADC for baremetal and cloud deployments.
• F5 Networks provides support and maintenance for the F5 BIG-IP Controller for Kubernetes.
• Gloo is an open-source ingress controller based on Envoy which offers API Gateway functionality with enterprise support from solo.io.
  
• HAProxy based ingress controller jcmoraisjr/haproxy-ingress which is mentioned on the blog post HAProxy Ingress Controller for Kubernetes. HAProxy Technologies offers support and maintenance for HAProxy Enterprise and the ingress controller jcmoraisjr/haproxy-ingress.
• Istio based ingress controller Control Ingress Traffic.
• Kong offers community or commercial support and maintenance for the Kong Ingress Controller for Kubernetes.
• NGINX, Inc. offers support and maintenance for the NGINX Ingress Controller for Kubernetes.
• Traefik is a fully featured ingress controller (Let’s Encrypt, secrets, http2, websocket), and it also comes with commercial support by Containous.

Using multiple Ingress controllers

You may deploy any number of ingress controllers within a cluster. When you create an ingress, you should annotate each ingress with the appropriate ingress.class to indicate which ingress controller should be used if more than one exists within your cluster.

If you do not define a class, your cloud provider may use a default ingress provider.

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

Note: Make sure you review your ingress controller’s documentation to understand the caveats of choosing it.

What's next

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

Feedback

Was this page helpful?

Thanks for the feedback. If you have a specific, answerable question about how to use Kubernetes, ask it on Stack Overflow. Open an issue in the GitHub repo if you want to report a problem or suggest an improvement.