perimeterx/px-extramodules repository overview

⁠Ingress NGINX Controller extraModule image with PerimeterX Enforcer Nginx module.

Important! px-extramodules version must match ingress-nginx version!

⁠Supported architectures: amd64 arm64 arm32v7

⁠Latest images

• v1.12.0 ingress-nginx with the latest stable PerimeterX Enforcer: perimeterx/px-extramodules:v1.12.0-latest
• v1.11.4 ingress-nginx with the latest stable PerimeterX Enforcer: perimeterx/px-extramodules:v1.11.4-latest
• v1.11.3 ingress-nginx with the latest stable PerimeterX Enforcer: perimeterx/px-extramodules:v1.11.3-latest

⁠Versioning schema

All images use the following naming/versioning schema: px-nginx-ingress-controller:vX.X.X-Y.Y.Y

Where:

• vX.X.X: is ingress-nginx version (ChangeLog: https://github.com/kubernetes/ingress-nginx/releases/⁠)
• Y.Y.Y: is PerimeterX Nginx Enforcer version (ChangeLog: https://docs.humansecurity.com/applications/nginx-intro/nginx-c-module-changelog⁠) . latest tag always contains the latest stable PerimeterX Enforcer version.

⁠Configuration

Information how to configure PX Nginx Enforcer could be found here: https://docs.humansecurity.com/applications-and-accounts/docs/ingress-nginx-enforcer-configuration-options⁠.

TAG and DIGEST can be found from the Docker Image.

⁠Example values.yaml

controller:
    extraModules:
      - name: px-enforcer
        image:
            registry: docker.io
            image: perimeterx/px-extramodules
            tag: TAG # must match the current ingress version
            digest: DIGEST
    config:
      main-snippet: |
        thread_pool px_pool threads=10;
        load_module /modules_mount/ngx_http_pxnginx_module.so;
      server-snippet: |
        px_enabled on;
        px_appId "--REPLACE--";
        px_cookie_secret "--REPLACE--";
        px_auth_token "--REPLACE--";

After editing values.yaml file, run the following command: helm upgrade nginx-ingress ingress-nginx/ingress-nginx --values values.yaml --install