Unable to deploy changes to configuration after upgrading haproxy-ingress from 3.1.14 to 3.2.10

[ronnybremer]

After upgrading to the latest helm charts the current haproxy-ingress version 3.2.3 was deployed. All existing routes are working perfectly.

However, after add a new TCP resource the following error can be seen on the haproxy-ingress pods:

2025/12/29 13:39:25 WARNING k8s/crs-deprecated-v1.go:210  Global CR defined in API ingress.v1.haproxy.org/v1 is DEPRECATED, please upgrade
2025/12/29 13:39:27 INFO    handler/tcp-cr.go:318 [transactionID=5866a7f6-0789-410b-b9bc-cd760fb4678b] reload required : TCP frontend 'tcpcr_mysql_f-mysql-prod' deleted
2025/12/29 13:39:27 INFO    haproxy/api/api.go:311 [transactionID=5866a7f6-0789-410b-b9bc-cd760fb4678b] reload required : backend 'ssl-backend' deleted
2025/12/29 13:39:27 INFO    haproxy/api/api.go:311 [transactionID=5866a7f6-0789-410b-b9bc-cd760fb4678b] reload required : backend 'mysql_svc_mysql-prod-cluster_mysql' deleted
2025/12/29 13:39:28 ERROR   controller/controller.go:182 [transactionID=5866a7f6-0789-410b-b9bc-cd760fb4678b] unable to Sync HAProxy configuration !!
2025/12/29 13:39:28 ERROR   controller/controller.go:183 [transactionID=5866a7f6-0789-410b-b9bc-cd760fb4678b] validation error: exit status 1: err transactionId=5866a7f6-0789-410b-b9bc-cd760fb4678b 
msg="Proxy 'ssl': unable to find required default_backend: 'ssl-backend'."
msg="Fatal errors found in configuration."
2025/12/29 13:39:28 ERROR   controller/controller.go:185 [transactionID=5866a7f6-0789-410b-b9bc-cd760fb4678b] read /etc/haproxy/failed: is a directory

I delete the new TCP and backend CRDs (this log actually shows the deletion), but even then, no changes can be made anymore. No SSL related parameters were changed, only a pass through TCP service configured.

The warning printed might have something to do with it, however, I do not find any CRD object in Global, Defaults, Backend or TCP.

[ronnybremer]

After the hard limit restart, changes are picked up without any issue. However, while the proxy is running pretty much every change to a CDR will trigger the error.

[hdurand0710]

Hi @ronnybremer,

However, while the proxy is running pretty much every change to a CDR will trigger the error.

This issue is the same I think as #765 and will be fixed in the next release 3.2 release.

[ronnybremer]

Thank you @hdurand0710. I will test it when the new release comes out.