Overview
This section provides guidance for installing Arize AX on Red Hat OpenShift, including Red Hat OpenShift Service on AWS (ROSA). The diagram below shows a typical OpenShift private-cloud topology.
Throughout this section, distribution archive means the Arize AX release tarball you download with your JWT (Helm chart, arize.sh, Terraform, examples, and offline HTML docs).
Read the ordered steps below once so you know the sequence (download -> cluster -> install -> ingress -> validate). Complete Prerequisites, including deployment types for your network model, before you start. Then open each linked page below; you can return here anytime as the hub.
For the full Helm reference, use Advanced -> Helm in the HTML documentation under docs/ inside your extracted distribution archive.
Download the distribution
Obtain the distribution archive with your JWT, extract it, and review the Helm chart, scripts, Terraform, and example manifests included in the bundle.
Download and extract
JWT,
get_latest.sh, folder layout, and what to open next.OpenShift cluster and infrastructure
Prepare namespaces, SCC-compatible security context values, object storage, storage classes, and registry access for the OpenShift target.
Existing OpenShift cluster
ROSA and private-cloud requirements, sizing, storage, namespaces, and SCC-aligned security context notes.
Install Arize AX
Configure
values.yaml for OpenShift and install the operator chart from the extracted distribution directory.Quick start
Example OpenShift
values.yaml and Helm command for a fast install path.Detailed walkthrough
Ceph/S3-compatible storage fields, base64 secrets, runAs IDs,
ingressMode, and arize.sh.Create ingress
Expose the UI and APIs with OpenShift ingress mode or the endpoint pattern your platform team standardizes on.
OpenShift ingress mode
Set
ingressMode: 'openshift', plan endpoint hostnames, and verify OpenShift routes or ingress resources.Configuring endpoints
Hostnames,
appBaseUrl, endpoint inventory, TLS, and DNS planning.Validate the deployment
Confirm pods are healthy, ingress and DNS resolve, and the UI is reachable before sending data.
Validation checklist
kubectl health checks, ingress inspection, login, and SDK testing.Use Arize AX
Open the public Arize AX documentation for product guides and configure your application with the on-prem SDK documentation.
Arize AX documentation
Product documentation, quickstarts, and observability guides on docs.arize.com.
SDK usage (self-hosted)
Python SDK versions and endpoint configuration for self-hosted deployments.
Integrations
Framework and provider integrations for tracing and monitoring.