Install Arize AX on GCP (quick start)

Prerequisites

Extracted tarball with arize-operator-chart.tgz and arize.sh in the current directory (Download and extract).
kubectl configured for your GKE cluster (GKE cluster and resources or Terraform).
For how to gather each value, base64 encoding, private registry image steps, and ./arize.sh, use the detailed walkthrough (GCP).

Helm install

From the directory that contains arize-operator-chart.tgz and your values.yaml:

helm upgrade --install -f values.yaml arize-op arize-operator-chart.tgz

Example `values.yaml` (GCP)

Adjust placeholders for your environment. After you edit the file, use the Minimum fields to verify table below as a line-by-line checklist before you run Helm.

cloud: "gcp"
clusterName: "gke_<project-id>_<region>_<cluster-name>"
# JWT from Arize AI, base64-encoded
hubJwt: "<JWT_BASE64>"
gazetteBucket: "<gazette-bucket-name>"
druidBucket: "<adb-bucket-name>"
# User-chosen secret, base64-encoded
postgresPassword: "<POSTGRES_PASSWORD_BASE64>"
organizationName: "<organization-or-company-name>"
# Encryption key, base64-encoded
cipherKey: "<CIPHER_KEY_BASE64>"
clusterSizing: "<sizing-option-from-arize-ai>"
gcpProject: "<project-id>"
# Service account email (plain text; Workload Identity binding target)
gcpServiceAccountName: "arize-platform@my-project.iam.gserviceaccount.com"
collectNodeMetrics: true

# URL for the Arize AX UI after ingress is configured
appBaseUrl: "https://<arize-app.domain>"

# Set to false only if not using Workload Identity
gcpWorkloadIdentityEnabled: true
# Required when Workload Identity is disabled — JSON key contents, base64-encoded
gcpServiceAccountJsonKey: "<JSON_KEY_BASE64>"

# Optional — private registry (same hostname for both; Artifact Registry or gcr.io)
pushRegistry: "us-central1-docker.pkg.dev/<project>/<repository>"
pullRegistry: "us-central1-docker.pkg.dev/<project>/<repository>"

# Optional — single shared node pool for base + historical
historicalNodePoolEnabled: false

Minimum fields to verify

Before helm upgrade --install, confirm every row below. If a cell is unclear, jump to the matching step in the detailed walkthrough.

Area	What to set
Identity	`hubJwt`, `organizationName`, `cipherKey`, `postgresPassword` (typically base64-encoded per chart docs)
GCP	`cloud: "gcp"`, `gcpProject`, `clusterName`, `gazetteBucket`, `druidBucket`, `gcpServiceAccountName` (plain email with Workload Identity)
Sizing	`clusterSizing` from Arize AI
UI URL	`appBaseUrl` once you know the hostname (can be updated after ingress)

Workload Identity

Keep gcpWorkloadIdentityEnabled: true unless your platform requires a JSON key. When Workload Identity is disabled, set gcpServiceAccountJsonKey to the full JSON key file contents, base64-encoded—see the detailed walkthrough.

Next steps

Detailed walkthrough (GCP) — step-by-step values, arize.sh, and optional mirroring

Architecture

Getting started

Platform

Ingress

Use Arize

Advanced

Resources

Install Arize AX on GCP (quick start)

Prerequisites

Helm install

Example `values.yaml` (GCP)

Minimum fields to verify

Workload Identity

Next steps

​Prerequisites

​Helm install

​Example values.yaml (GCP)

​Minimum fields to verify

​Workload Identity

​Next steps

​Related

Prerequisites

Helm install

Example `values.yaml` (GCP)

Minimum fields to verify

Workload Identity

Next steps

Related