Plans to move to V3 of ModSecurity? about modsecurity-spoa HOT 5 CLOSED

Yep, this should be as simple as update dependencies but the problem is the existence of a good wrapper. HAProxy's one is good enough but V2 only. A co worker has started an attempt to write one but didn't evolve. This might be my next challenge in the near future, and let me know if you find a good wrapper out there that talks HAProxy's spop.

from modsecurity-spoa.

Hmm. I don't think I have the expertise to write a wrapper for V3.
I'm testing a more kubernetes native approach to the memory leaks in V2 of ModSecurity.
I think once I confirm it works, I can bring it into a docs change for HAProxy.
Largely it just setting resource limits to kill the ModSecurity process on the container and adding a liveness probe for the default port to restart the pod if ModSecurity is not available.

from modsecurity-spoa.

I've made the following PR to the docs: jcmoraisjr/haproxy-ingress#841
This can be closed.

from modsecurity-spoa.

Hello,
Have any of you tried this? > https://github.com/corazawaf/coraza-spoa
Regards

from modsecurity-spoa.

Yes, I have actually tested it for the ingress controller that @jcmoraisjr maintains. It works.
We even added documentation on how to swap it in place.

from modsecurity-spoa.