Detailed walkthrough (OpenShift)

Before you start

Complete Download and extract the distribution. Work from the extracted folder that contains arize.sh, arize-operator-chart.tgz, and your values.yaml.
Align your cluster with OpenShift cluster and resources.
Contact Arize AI for clusterSizing. It must match your cluster capacity.
Keep the OpenShift quick start open as a template.
Treat values.yaml as sensitive. Store generated passwords and keys in your secret manager, not in git history.

For every field that must be base64-encoded, use:

printf '%s' '<plain-text-value>' | base64 | tr -d '\n'

1. Verify cluster access and clusterName

Confirm the target cluster is reachable:

kubectl config current-context
kubectl get nodes

Set clusterName to the OpenShift cluster name your platform team uses for this deployment:

clusterName: "<cluster-name>"

2. Seed hubJwt

Store the runtime registry JWT Arize AI provided under hubJwt, base64-encoded:

hubJwt: "<JWT_BASE64>"

3. Configure object storage

For a Ceph or S3-compatible endpoint, set:

cloud: "ceph"
gazetteBucket: "<gazette-bucket-name>"
druidBucket: "<adb-bucket-name>"
cephS3Endpoint: "<URL to the Ceph S3 endpoint>"
cephS3AccessKeyId: "<base64-encoded-ceph-s3-access-key-id>"
cephS3SecretAccessKey: "<base64-encoded-ceph-s3-secret-access-key>"

Pre-provision the Gazette and ArizeDB buckets and grant the credentials read/write access before installing.

4. Set secrets, organization, and sizing

Choose a Postgres password and cipher key, base64-encode them, and set the organization and sizing values:

postgresPassword: "<POSTGRES_PASSWORD_BASE64>"
cipherKey: "<CIPHER_KEY_BASE64>"
organizationName: "<name of the organization or company>"
clusterSizing: "<sizing option>"

5. Align security context values

Set runAs and fsGroup values to match the SCC policy for the namespaces Arize AX will use:

baseRunAsUser: 1000
baseRunAsGroup: 1000
baseFsGroup: 1000
postgresRunAsUser: 70
postgresRunAsGroup: 70
postgresFsGroup: 70
operatorRunAsUser: 1000
operatorRunAsGroup: 1000
operatorFsGroup: 1000

The numbers above are placeholders from the example. Replace them with values approved for your OpenShift namespaces.

6. Set appBaseUrl and ingressMode

Set the URL users will use for the Arize AX UI after ingress and DNS exist:

appBaseUrl: "https://<arize-app.domain>"

Use OpenShift ingress mode:

ingressMode: 'openshift'

Use OpenShift ingress mode and Configuring ingress and endpoints to plan hostnames, TLS, and endpoint exposure.

7. Optional private registry

If the cluster must pull images from your registry, set both registry values:

pushRegistry: "<container-registry>"
pullRegistry: "<container-registry>"

8. Install with arize.sh or Helm

Using arize.sh:

./arize.sh -y install

Using Helm directly:

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

Both approaches install the operator chart using the same values.yaml.

Reinstall cleanup

To remove an existing Arize AX install from this cluster before reinstalling, follow Fresh reinstall cleanup. That procedure is destructive; use it only when you intentionally want to discard the existing install.

​Before you start

​1. Verify cluster access and clusterName

​2. Seed hubJwt

​3. Configure object storage

​4. Set secrets, organization, and sizing

​5. Align security context values

​6. Set appBaseUrl and ingressMode

​7. Optional private registry

​8. Install with arize.sh or Helm

​Reinstall cleanup

​Next steps