Skip to main content

​
Overview

Use this page when you already have a Red Hat OpenShift cluster, including Red Hat OpenShift Service on AWS (ROSA), and will align storage, namespaces, registry access, and security context settings for Arize AX.

​
Requirements

Before installing on OpenShift, prepare:
  • A working kubeconfig for the target OpenShift cluster.
  • Object storage for Gazette and ArizeDB data. Private-cloud OpenShift installs commonly use Ceph or another S3-compatible endpoint.
  • Block-storage-backed storage classes for standard persistent volumes and SSD-style persistent volumes. Do not use NFS-backed storage classes.
  • Dedicated namespaces for Arize AX, typically arize and arize-operator. The installer creates them by default; if your platform pre-creates namespaces, set createNamespaces: false.
  • Namespace and security context settings that align with your OpenShift SCC policy.
  • The application URL you plan to expose Arize AX at, for appBaseUrl.
  • Optional private registry access if the cluster cannot pull directly from Arize AI’s central image registry.

​
Sizing

Contact Arize AI for the clusterSizing field. This field controls the deployment size and must align with the size of the cluster. Common production values are small1b and medium2b.

​
Object storage

Provide two buckets or bucket-equivalent paths:
  • One bucket for Gazette data.
  • One bucket for ArizeDB data.
For Ceph or another S3-compatible endpoint, collect the endpoint URL plus an access key and secret key that can read and write both buckets.

​
Namespaces and security contexts

Use dedicated namespaces for Arize AX. The examples use arize and arize-operator; if you choose different names, keep them dedicated to this Arize AX install and set namespaceArize or namespaceOperator in values.yaml. If your platform pre-creates the namespaces, set createNamespaces: false. OpenShift security context constraints usually require explicit runAs and fsGroup values. Align the baseRunAsUser, baseRunAsGroup, baseFsGroup, postgresRunAsUser, postgresRunAsGroup, postgresFsGroup, operatorRunAsUser, operatorRunAsGroup, and operatorFsGroup values with your namespace policy before installing.

​
Optional image registry

A private registry is optional when pulling from Arize AI’s central image registry. If your cluster cannot pull directly from that registry, configure image mirroring and set pushRegistry and pullRegistry in values.yaml.

​
Next steps