Release notes

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

Version 1.9 Jump to heading #

About this release Jump to heading #

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

• Upgraded to HAProxy Enterprise 2.6
• Prometheus metrics for config snippets
• RedHat Docker image
• External mode configuration file

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

Upgraded HAProxy Enterprise

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

Prometheus metrics for config snippets

• The Prometheus endpoint, which provides network traffic metrics, now includes metrics that will help when troubleshooting config snippets. Errors in config snippet files can prevent them from loading. The metric haproxy_active_backend_config_snippets shows successfully loaded, active config snippets; haproxy_inactive_backend_config_snippets shows inactive snippets that didn’t load correctly; haproxy_unable_to_sync_configuration shows a 1 if any config snippet are inactive or a 0 otherwise.

RedHat Docker image

• You can now deploy the ingress controller’s RedHat Enterprise Linux Docker image, hapee-ingress-ubi.

External mode configuration file

• You can store startup arguments in a YAML file when running in external mode. Use the startup argument --config-file to set the YAML file to load.

Other improvements

• The Global, Defaults, and Backend custom resources received minor updates.
• We added trace logs for endpoints and servers. Set the startup argument --log=trace to see trace-level logs.

Version 1.8 Jump to heading #

About this release Jump to heading #

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

• A new configuration file option
• An integrated default backend service
• Upgraded to HAProxy Enterprise 2.5
• Security enhancements
• Debugging enhancements

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

New configuration file

• Startup arguments that previously had to be set as command-line arguments can now be saved in a YAML file by using the --config-file argument, promoting reusability.

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 Enterprise

• This version upgrades to HAProxy Enterprise 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.