Release notes

The release notes give you an overview of the what’s new, updated, and removed in this version of HAProxy Kubernetes Ingress Controller.

Version 1.10 Jump to heading #

About this release Jump to heading #

Key changes in the HAProxy Kubernetes Ingress Controller 1.10 release include:

• Upgraded HAProxy
• New Docker image tags
• Dropped support for Beta versions of Ingress
• Matching of CPU quotas
• Partial support for Gateway API (TCPRoute)

What’s new, improved and removed Jump to heading #

Upgraded HAProxy

• This version upgrades to HAProxy 2.7 as the underlying load balancer engine.

Docker image tags

• The haproxytech/kubernetes-ingress Docker image now has major.minor version tags, such as 1.8, 1.9, and 1.10 so that users can more easily pin their deployment to a specific version.

Dropped support for Beta versions of Ingress

• We no longer support the deprecated Kubernetes APIs extensions/v1beta1 and networking.k8s.io/v1beta1 on Ingress resources. Instead, use networking.k8s.io/v1.

Matching of CPU quotas

• The ingress controller now sets its GOMAXPROCS variable to match the match the Linux container’s CPU quota, providing better performance.

Gateway API (TCPRoute)

• Added support for the TCPRoute resource in Gateway API. This provides a new way of routing TCP traffic, as an alternative to the --configmap-tcp-services startup argument.

Version 1.9 Jump to heading #

About this release Jump to heading #

Key changes in the HAProxy Kubernetes Ingress Controller 1.9 release include:

• Upgraded to HAProxy 2.6

What’s new, improved and removed Jump to heading #

Upgraded HAProxy

• This version upgrades to HAProxy 2.6 as the underlying load balancer engine.

Version 1.8 Jump to heading #

About this release Jump to heading #

Key changes in the HAProxy Kubernetes Ingress Controller 1.8 release include:

• An integrated default backend service
• Upgraded to HAProxy 2.5
• Security enhancements
• Debugging enhancements

What’s new, improved and removed Jump to heading #

Default backend

• When no ingress rules match, the ingress controller displays a default Not Found web page. To enable this in prior versions, you had to set the startup argument --default-backend-service. This is no longer necessary. The ingress controller will self host a web page for this purpose, reducing the number of services deployed to your Kubernetes cluster.

Upgraded HAProxy

• This version upgrades to HAProxy 2.5 as the underlying load balancer engine.

Security enhancements

• The ingress controller process now runs as a non-root user inside its Docker container while keeping the ability to bind to privileged ports 80 and 443.
• The annotations blacklist and whitelist, which you can use to allow or deny ranges of IP addresses, now accept a file that stores the IP addresses.
• The new annotation client-strict-sni returns an error if no certificate is found for a client SNI.

Debugging

• Since version 1.7, if you include the --pprof startup argument the ingress controller exposes pprof debug data at port 6060 at the URL path /debug/pprof. Now you can change the port by specifying the --controller-port argument.
• If you set the startup argument --prometheus, new Prometheus metrics are exposed at port 6060 at the URL path /metrics. They include diagnostic information such as the amount of memory allocated to the process and CPU time spent.