Releases: wallarm/ingress
Releases · wallarm/ingress
4.2.4+upstream4.3.0
4.2.3+upstream4.2.5
- The Helm chart version of the NGINX Ingress controller has been bumped to 4.2.5
4.2.2+upstream4.2.4
- The Helm chart version of the NGINX Ingress controller has been bumped to 4.2.4
- The NGINX Ingress controller version has been bumped to 1.3.1
- New NGINX Ingress controller version patches the CVE-2022-1996 vulnerability
- The NGINX Ingress controller now sends data to the postanalytics module using K8s Service DNS address
4.2.1+upstream4.2.3
- The Helm chart version of the NGINX Ingress controller has been bumped to 4.2.3
4.2.0+upstream4.2.1
- Upgrade the Wallarm node module up to 4.2
- The Helm chart version of the NGINX Ingress controller has been bumped to 4.2.1
4.0.6+upstream4.2.0
- Fixed problem with zombie processes arose by supercronic
4.0.5+upstream4.2.0
- The NGINX Ingress controller version has been bumped to 1.3.0.
- The default port of the Wallarm API endpoints has been changed to 443 where it was missed. Even if the
apiPort
parameter is not specified in the values.yaml file, its value remains 443. - The Supercronic version has been bumped to 0.2.1.
- The appstructure Wallarm component now can access Wallarm API via an HTTP(S) proxy server specified in the environment variables. It allows the API Discovery module to send correct data to the Wallarm Cloud accessed via the proxy server.
4.0.4+upstream4.1.4
- The Helm chart version of the NGINX Ingress controller has been bumped to 4.1.4
4.0.3+upstream4.1.3
- The NGINX Ingress controller version has been bumped to 1.2.1
- New NGINX Ingress controller version patches the CVE-2021-25745 vulnerability
4.0.2+upstream4.0.19
- The new Ingress annotation nginx.ingress.kubernetes.io/wallarm-partner-client-uuid to set the unique identifier of the tenant for the multi-tenant nodes