gulecroc

Same problem for me with the default configuration. When I enabled log trace I found that the connector was not batching messages (99% of time batching 1 message). To show...

@BernhardGruen you'are right, I was waiting for the release. Fix in v1.9.6. Thanks you @iliuta

I just upgrade chart v4.8.4 to v4.9.1 with controller v1.9.6, but the modseurity lib version is still v3.0.8 : ``` "producer": { "components": [ "OWASP_CRS/3.3.5\"" ], "secrules_engine": "DetectionOnly", "connector": "ModSecurity-nginx...

@iliuta to test it, I add a custom rule to my Ingress (could be set on the chart too) : ``` apiVersion: networking.k8s.io/v1 kind: Ingress metadata: annotations: nginx.ingress.kubernetes.io/modsecurity-snippet: | SecRuleEngine...

Hi @strongjz, Do you have any idea why after upgrade chart to v4.9.1 with controller v1.9.6, the modsecurity version is still v3.0.8 ? I checked the branch and it seems...

/reopen Hi @strongjz and @rikatz, The controller shows modsecurity v3.0.12 in the logs : ``` "producer": { "modsecurity": "ModSecurity v3.0.12 (Linux)", "connector": "ModSecurity-nginx v1.0.3", "secrules_engine": "DetectionOnly", "components": [ "OWASP_CRS/3.3.5\"" ]...

Hi @slickwarren, Same behavior on rancher provisioned cluster with RKE1, or with custom cluster RKE1. I open an other issue because our clusters are declared in the old fleet namespace,...

We can find community images here : https://hub.docker.com/u/greenbone Documentation : https://greenbone.github.io/docs/latest/

Hi @lhotari, we would like to you OIDC support too, can someone review this PR ? Thank you

Thank you @lhotari, I start working with @brunodomenici on your reviews