Open anderius opened 2 months ago
Hi @anderius thanks for reporting!
Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this :slightly_smiling_face:
Cheers!
I'm also facing similar issue.
Hi Folks, we are currently looking into this.
Hi folks @anderius @janibashamd
We've been in contact with the team that owns the development of this component of AppProtect v5. They are working on ensure the waf-enforcer
wont crash in this scenario.
As soon as we have more info, we'll share it in this thread.
Describe the bug Enforcer container fails to start without sites configured. NginxIC container also fails to start, waiting for the enforcer container.
To Reproduce Deploy the Helm chart with Nginx App Protect V5 enabled, but no resources that uses the WAF. That is, no VirtualServer with apBundle.
Expected behavior We expect the nginx ic and the enforcer container to start without errors, even when no virtualserver with WAF is deployed.
Your environment
Additional context Log from the enforcer container: