Releases: wallarm/ingress
4.10.6+upstream4.9.0
-
Added the
controller.wallarm.container_name.extraEnvs
chart values to allow passing additional environment variables to Docker containers utilized by the solution -
Enhanced OpenAPI data type detection by the API Discovery module
-
Introduced the
wallarm_http_v2_stream_max_len
directive to control the maximum length of HTTP/2 streams, helping prevent excessive memory consumption in long-lived gRPC connectionsTo apply this directive during Ingress controller deployment, include it in the
controller.config.http-snippet
,server-snippet
, orlocation-snippet
values. Alternatively, use thenginx.ingress.kubernetes.io/server-snippet
Ingress annotation. -
Resolved a memory leak issue where memory continued to be consumed after an overlimit attack was triggered, even when no further attack checks were conducted
4.10.5+upstream4.9.0
- Fixed the API Abuse Prevention module logging issues
4.10.4+upstream4.9.0
- Added support for applying limits on GraphQL requests
- API specifications enforcement
- New APIFW v0.7.2
4.8.9+upstream4.9.0
Fixed performance issue
4.10.3+upstream4.9.0
- Update of appstructure package
- Improved node sync logic
4.8.8+upstream4.9.0
- Fixed an issue where partially downloaded custom ruleset files were mistakenly validated as complete. Chunked downloading has been implemented to address this issue
4.10.2+upstream4.9.0
- Restored OpenTracing
4.10.1+upstream4.9.0
-
Updated the
appstructure
package -
Internal enhancements and optimizations:
- Implemented labels and annotations for the Tarantool pod
- Transitioned Wallarm helper container to supervisord
-
Fix CVEs in Wallarm helper image:
4.8.7+upstream4.9.0
- Restored OpenTracing for 4.8 versions
4.10.0+upstream4.9.0
- Upgrade the Wallarm node module to version 4.10
- Fixed CVE-2024-21626