Configuration Reference

These options can be stored in a ConfigMap to change the ingress controller's global behavior, affecting all Ingress routes.

The Backend custom resource extends the Kubernetes API to let you manage how traffic is load balanced across pods.

The Defaults custom resource extends the Kubernetes API to let you manage default load balancer settings that apply to all services.

The Frontend custom resource extends the Kubernetes API to let you manage frontends that ingress controller generates.

The Global custom resource extends the Kubernetes API to let you manage process-level options for the ingress controller.

These annotations can be set in an Kubernetes Ingress object's metadata.annotations section to change how requests are routed for a particular service.

An Ingress resource can target a specific Ingress controller instance, which is useful when running multiple ingress controllers in the same cluster.

These annotations can be set in a Kubernetes Service object's metadata.annotations section to change how requests are routed for a particular service.

You can customize the HAProxy Enterprise Kubernetes Ingress Controller by passing these arguments at startup. These affect the lifetime of the process.

TCP CRD.

The Backend custom resource extends the Kubernetes API to let you manage how traffic is load balanced across pods.

Values files can be used in place of command line invocations and can be used to override default configuration values.