Installation on standard cluster

A GKE Standard cluster provides full control over node configuration, including ephemeral storage limits for pods. Nodes are distributed across zones for high availability.

Cluster configuration

Recommended configuration Value
Mode Standard (user-managed nodes)
Region <User-defined>
Machine type Tested/validated reference: n2-standard-16 (16 vCPU / 64 GB memory). Adjust based on your organization's concurrent scan volume — see Environment setup resources for platform and per-scan-type resource requirements.
Boot disk Tested/validated reference: 250 GB SSD persistent disk (pd-ssd). Increase if you select a larger machine type or expect higher concurrent scan volume.
Kubernetes version Current GKE default version (Regular release channel). AppScan 360° does not require a specific minimum version.
Node autoscaling 0–3 nodes — Increase based on your expected concurrent scan volume.
NAP (Node Auto Provisioning) Disabled
VPC network <your-vpc-network>
Subnet <your-app-subnet>
Network mode VPC-native
Workload Identity Enabled
Vertical Pod Autoscaling Enabled
Shielded nodes Enabled
Logging / Monitoring Cloud Logging, Cloud Monitoring + Managed Prometheus

Enabled add-ons

Enable the following add-ons while setting up cluster:

  • Filestore CSI Driver
  • GCE Persistent Disk CSI Driver
  • GCS Fuse CSI Driver
  • NodeLocal DNS Cache
  • HTTP Load Balancing
  • Gateway API (CHANNEL_STANDARD)

Installing AppScan 360°

Before creating the cluster:

Once the cluster setup is complete, use the GKE Cloud Shell or a local deployer machine to install AppScan 360° following the standard Helm installation instructions.