Upgrading Wallarm Native Node with Helm Chart¶
These instructions describe the steps to upgrade the Native Node deployed using Helm chart.
Requirements¶
The Kubernetes cluster for deploying the Native Node with the Helm chart must meet the following criteria:
-
Helm v3 package manager installed.
-
Inbound access from your API gateway or CDN where your APIs are running.
-
Outbound access to:
https://charts.wallarm.com
to download the Wallarm Helm charthttps://hub.docker.com/r/wallarm
to download the Docker images required for the deploymenthttps://us1.api.wallarm.com
orhttps://api.wallarm.com
for US/EU Wallarm Cloud-
IP addresses below for downloading updates to attack detection rules and API specifications, as well as retrieving precise IPs for your allowlisted, denylisted, or graylisted countries, regions, or data centers
-
In addition to the above, you should have the Administrator role assigned in Wallarm Console.
1. Update the Wallarm Helm chart repository¶
2. Upgrade the Wallarm Kubernetes service¶
Upgrade the deployed Kubernetes service or Load Balancer:
helm upgrade <RELEASE_NAME> -n <NAMESPACE> wallarm/wallarm-node-native --version 0.12.0 -f <PATH_TO_VALUES>
-
<RELEASE_NAME>
: the name of the existing Helm release -
<NAMESPACE>
: the namespace with the Helm release -
<PATH_TO_VALUES>
: the path to thevalues.yaml
file defining the deployed solution configurationWhen upgrading to version 0.10.1 or higher, remove the
config.connector.log_level
parameter if specified. It has been replaced by theconfig.connector.log
section for more granular logging. Specify thelog.*
parameters if customization is needed.
3. Verify the upgrade¶
-
Verify that the Wallarm pods are up and running:
Each pod status should be STATUS: Running or READY: N/N. For example:
-
Send the request with the test Path Traversal attack to your API gateway:
-
Verify that the upgraded node operates as expected compared to the previous version.