Skip to content

Deploying NGINX Ingress Controller with Integrated Wallarm Services

These instructions provide you with the steps to deploy the Wallarm NGINX-based Ingress controller to your K8s cluster. The solution involves the default functionality of Community Ingress NGINX Controller with integrated Wallarm services.

The solution has the following architecture:

Solution architecture

The solution is deployed from the Wallarm Helm chart.

Use cases

Among all supported Wallarm deployment options, this solution is the recommended one for the following use cases:

  • There is no Ingress controller and security layer routing traffic to Ingress resources compatible with Community Ingress NGINX Controller.

  • You are using Community Ingress NGINX Controller and looking for a security solution compatible with your technology stack.

    You can seamlessly replace the deployed NGINX Ingress Controller with the one these instructions describe by only moving your configuration to a new deployment.


  • Kubernetes platform version 1.24-1.27

  • Helm package manager

  • Compatibility of your services with the Community Ingress NGINX Controller version 1.8.1

  • Access to the account with the Administrator role and two‑factor authentication disabled in Wallarm Console for the US Cloud or EU Cloud

  • Access to for working with US Wallarm Cloud or to for working with EU Wallarm Cloud

  • Access to to add the Wallarm Helm charts. Ensure the access is not blocked by a firewall

  • Access to the Wallarm repositories on Docker Hub Make sure the access is not blocked by a firewall

  • Access to the IP addresses of Google Cloud Storage listed within the link. When you allowlist, denylist, or graylist entire countries, regions, or data centers instead of individual IP addresses, the Wallarm node retrieves precise IP addresses related to the entries in the IP lists from the aggregated database hosted on Google Storage

Known restrictions

  • Operation without the postanalytics module is not supported.

  • Scaling down postanalytics module may result in a partial loss of attack data.


  1. Install the Wallarm Ingress controller.

  2. Enable traffic analysis for your Ingress.

  3. Check the Wallarm Ingress controller operation.

Step 1: Installing the Wallarm Ingress Controller

To install the Wallarm Ingress Controller:

  1. Generate a filtering node token of the appropriate type:

    1. Open Wallarm Console → SettingsAPI tokens in the US Cloud or EU Cloud.
    2. Find or create API token with the Deploy source role.
    3. Copy this token.
    1. Open Wallarm Console → Nodes in either the US Cloud or EU Cloud.
    2. Create a filtering node with the Wallarm node type and copy the generated token.

      Creation of a Wallarm node

  2. Create a Kubernetes namespace to deploy the Helm chart with the Wallarm Ingress controller:

    kubectl create namespace <KUBERNETES_NAMESPACE>
  3. Add the Wallarm chart repository:

    helm repo add wallarm
  4. Create the values.yaml file with the Wallarm configuration. Example of the file with the minimum configuration is below.

    When using an API token, specify a node group name in the nodeGroup parameter. Your node will be assigned to this group, shown in the Wallarm Console's Nodes section. The default group name is defaultIngressGroup.

        enabled: "true"
        token: "<NODE_TOKEN>"
        apiHost: ""
        # nodeGroup: defaultIngressGroup
        enabled: "true"
        token: "<NODE_TOKEN>"
        # nodeGroup: defaultIngressGroup

    You can also store the Wallarm node token in Kubernetes secrets and pull it to the Helm chart. Read more

  5. Install the Wallarm packages:

    helm install --version 4.6.8 <RELEASE_NAME> wallarm/wallarm-ingress -n <KUBERNETES_NAMESPACE> -f <PATH_TO_VALUES>
    • <RELEASE_NAME> is the name for the Helm release of the Ingress controller chart
    • <KUBERNETES_NAMESPACE> is the Kubernetes namespace you have created for the Helm chart with the Wallarm Ingress controller
    • <PATH_TO_VALUES> is the path to the values.yaml file

Step 2: Enabling traffic analysis for your Ingress

kubectl annotate ingress <YOUR_INGRESS_NAME> -n <YOUR_INGRESS_NAMESPACE>
  • <YOUR_INGRESS_NAME> is the name of your Ingress

  • <YOUR_INGRESS_NAMESPACE> is the namespace of your Ingress

  • <APPLICATION> is a positive number that is unique to each of your applications or application groups. This will allow you to obtain separate statistics and to distinguish between attacks aimed at the corresponding applications

Step 3: Checking the Wallarm Ingress Controller operation

  1. Get the list of pods:

    kubectl get pods -n <NAMESPACE> -l

    Each pod should display the following: STATUS: Running and READY: N/N. For example:

    NAME                                                              READY     STATUS    RESTARTS   AGE
    ingress-controller-nginx-ingress-controller-675c68d46d-cfck8      4/4       Running   0          5m
    ingress-controller-nginx-ingress-controller-wallarm-tarantljj8g   4/4       Running   0          5m
  2. Send the request with the test Path Traversal attack to the Ingress Controller Service:

    curl http://<INGRESS_CONTROLLER_IP>/etc/passwd

    If the filtering node is working in the block mode, the code 403 Forbidden will be returned in the response to the request and the attack will be displayed in Wallarm Console → Events.


After the Wallarm Ingress controller is successfully installed and checked, you can make advanced configurations to the solution such as:

To find parameters used for advanced configuration and appropriate instructions, please follow the link.