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.

    You may deploy any number of ingress controllers using ingress class 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 ). is a replacement of the older annotation method.

    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.