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 binary, Ingress controllers are not started automatically with a cluster. Use this page to choose the ingress controller implementation that best fits your cluster.

    Note: This section links to third party projects that provide functionality required by Kubernetes. The Kubernetes project authors aren’t responsible for these projects, which are listed alphabetically. To add a project to this list, read the before submitting a change. More information.

    • is an ingress controller that configures the Azure Application Gateway.
    • API Gateway is an Envoy-based ingress controller.
    • is an Apache APISIX-based ingress controller.
    • provides L4-L7 load-balancing using VMware NSX Advanced Load Balancer.
    • is a BFE-based ingress controller.
    • is an Envoy based ingress controller.
    • is an Envoy based API gateway that can run as an ingress controller.
    • is an Easegress based API gateway that can run as an ingress controller.
    • F5 BIG-IP lets you use an Ingress to configure F5 BIG-IP virtual servers.
    • Gloo is an open-source ingress controller based on , which offers API gateway functionality.
    • HAProxy Ingress is an ingress controller for .
    • The HAProxy Ingress Controller for Kubernetes is also an ingress controller for .
    • Istio Ingress is an based ingress controller.
    • Kusk Gateway is an OpenAPI-driven ingress controller based on .
    • The NGINX Ingress Controller for Kubernetes works with the webserver (as a proxy).
    • The Pomerium Ingress Controller is based on , which offers context-aware access policy.
    • Skipper HTTP router and reverse proxy for service composition, including use cases like Kubernetes Ingress, designed as a library to build your custom proxy.
    • The is an ingress controller for the Traefik proxy.
    • extends Ingress with Custom Resources to bring API Management capabilities to Ingress. Tyk Operator works with the Open Source Tyk Gateway & Tyk Cloud control plane.
    • Voyager is an ingress controller for .

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

    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.

    • Learn more about .