You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
daemon.err: Jan 12 10:56:01 reloader: [ALERT] 011/105601 (51) : parsing [/etc/haproxy/haproxy.cfg:36] : error detected in frontend 'http-0_0_0_0-80' while parsing redirect rule : error in condition: no such ACL : 'host_acl_test1.example.com'.
daemon.err: Jan 12 10:56:01 reloader: [ALERT] 011/105601 (51) : Error(s) found in configuration file : /etc/haproxy/haproxy.cfg
daemon.err: Jan 12 10:56:01 reloader: [ALERT] 011/105601 (51) : Fatal errors found in configuration.
The HTTPS frontend, instead, has the acl as it should be. Creating more than one host rules triggers the creation of the missing ACL for all HTTP frontends.
The bug is indeed when having only one host rule and no default backend.
The text was updated successfully, but these errors were encountered:
Version 5.0.0.rc11
Create an ingress like this one:
No default backend, only one host rule. The generated frontend for HTTP looks like this:
And of course the pod fails like this:
The HTTPS frontend, instead, has the acl as it should be. Creating more than one host rules triggers the creation of the missing ACL for all HTTP frontends.
The bug is indeed when having only one host rule and no default backend.
The text was updated successfully, but these errors were encountered: