Skip to content

Fine‑tuning of Wallarm Ingress Controller

Official documentation for NGINX Ingress Controller

The fine‑tuning of Wallarm Ingress Controller is quite similar to that of NGINX Ingress Controller described in the official documentation. When working with Wallarm, all options for setting up the original NGINX Ingress Controller are available.

Additional Settings for Helm Chart

The settings are performed via the values.yaml file. By default, the file looks as follows:

    enabled: false
    apiPort: 444
    apiSSL: true
    token: ""
      kind: Deployment
        annotations: {}
      replicaCount: 1
      arena: "0.2"
        failureThreshold: 3
        initialDelaySeconds: 10
        periodSeconds: 10
        successThreshold: 1
        timeoutSeconds: 1
      resources: {}
      enabled: false


        ## List of IP addresses at which the stats-exporter service is available
        ## Ref:
        externalIPs: []

        loadBalancerIP: ""
        loadBalancerSourceRanges: []
        servicePort: 9913
        type: ClusterIP
      resources: {}
      resources: {}
      enabled: false
      resources: {}

A description of the main parameters you can set up is provided below. Other parameters come with default value and rarely need to be changed; their descriptions are provided at this link.


Allows you to enable or disable Wallarm functions.

Default value: false


Wallarm API endpoint. Can be:

Default value:


The Cloud Node token is created on the Wallarm portal in the EU or US cloud. It is required to access to Wallarm API.

Default value: not specified


The number of running pods for postanalytics. Postanalytics is used for the behavior‑based attack detection.

Default value: 1


Specifies the amount of memory allocated for postanalytics service. It is recommended to set up a value sufficient to store requests data for the last 5-15 minutes.

Default value: 0.2


This switch toggles information and metrics collection. If Prometheus is installed in the Kubernetes cluster, no additional configuration is required.

Default value: false

Global Controller Settings

Implemented via ConfigMap.

Besides the standard ones, the following additional parameters are supported:

Ingress Annotations

These annotations are used for setting up parameters for processing individual instances of Ingress.

Besides the standard ones, the following additional annotations are supported:

To apply the settings to your Ingress, please use the following command:

kubectl annotate --overwrite ingress YOUR_INGRESS_NAME ANNOTATION_NAME=VALUE
  • YOUR_INGRESS_NAME is the name of your Ingress,

  • ANNOTATION_NAME is the name of the annotation from the list above,

  • VALUE is the value of the annotation from the list above.

For example, to enable IP blocking, create the addresses list in your Wallarm account and execute the following command:

kubectl annotate --overwrite ingress YOUR_INGRESS_NAME