Kubernetes cluster deployment requirements (optional)

To deploy Application Security to a Kubernetes cluster, make sure that the following requirements are met.

Kubernetes cluster requirements

The following are the minimum requirements for the default installation:

  • Kubernetes versions 1.32, 1.33, or 1.34

  • Kubernetes persistent volumes with optional support for Pod security context fsGroup option

    Using a non-default container user ID requires fsGroup support.

  • Kubernetes LoadBalancer Service type (recommended)

  • 28 GB of available RAM and 8 CPUs on a single Kubernetes node

  • 4 GiB of storage for persistent volume

Locally-installed tools required

  • A kubectl command-line tool

    OpenText recommends that you use the same kubectl command-line tool version as the Kubernetes cluster version or follow the Version Skew Policy on the Kubernetes website.

  • Helm command-line tool versions 3.18 or 3.19

    To determine which Helm command-line tool version matches your Kubernetes cluster version, see the Helm Version Support Policy on the Helm website.

  • (Recommended) A Docker® client and server installation (any version)

Additional requirements

  • Kubeconfig file for the Kubernetes cluster

  • Docker Hub account with access to Application Security images

    If you need access to the Fortify Docker repository, contact mfi-fortifydocker@opentext.com with your first name, your last name, and your Docker ID. OpenText will then give you access to the Docker organization that contains the Application Security images.

  • DNS name for the Application Security web application (address used to access the service)

  • Java keystore for setting up HTTPS

    The keystore must contain a CA certificate and a server certificate for the Application Security DNS name with an associated private key.

    • Keystore password

    • Private key password

  • Fortify license file