Skip to main content

​
Overview

Use this page when Kubernetes is already running and is managed by Rancher. Rancher can manage clusters across cloud, private cloud, and bare-metal infrastructure; this guide starts from an existing Rancher-managed Kubernetes cluster and does not cover provisioning Rancher or the underlying hosts. Your platform team owns the cluster-level choices: storage classes, ingress, DNS, registry access, and object storage. The Arize AX install flow is still the same: point kubectl at the target cluster, create values.yaml next to arize.sh, then run ./arize.sh install from the extracted distribution directory. Throughout this section, distribution archive means the Arize AX release tarball you download with your JWT (Helm chart, arize.sh, examples, and offline HTML docs). Read the ordered steps below once so you know the sequence (download -> cluster/storage -> values -> install -> ingress -> validate). Then open each linked page below; you can return here anytime as the hub.
1

Download the distribution

Obtain the distribution archive with your JWT, extract it, and review the Helm chart, scripts, examples, and offline docs included in the bundle.

Download and extract

JWT, get_latest.sh, folder layout, and what to open next.
2

Prepare cluster and storage

Confirm kubeconfig, namespaces, storage classes, object storage, sizing, and Rancher-specific cluster constraints before installing.

Cluster and storage

Kubeconfig, namespaces, object storage, sizing, small-cluster values, tolerations, and baseOverlay guidance.
3

Install Arize AX

Create values.yaml in the extracted distribution directory, run the installer, and apply platform-specific adjustments when needed.

Install Arize AX

Create values.yaml, encode secrets, run ./arize.sh -y -t 5400 install, and handle namespace ownership.

Restricted PodSecurity

Promtail hostPath, PodSecurity baseline, and policy guidance.
4

Create ingress

Expose the UI and APIs with the ingress controller, load balancer, DNS, and TLS pattern your platform team standardizes on.

Configuring endpoints

Hostnames, appBaseUrl, endpoint inventory, TLS, and DNS planning.

NGINX, Istio, Kong, ...

Example paths under examples/endpoints and ingressMode guidance.
5

Validate and troubleshoot

Check operator status, pods, jobs, and logs. Use cleanup guidance only when intentionally discarding a previous install.

Validate and troubleshoot

Operator status, pods, jobs, stuck-job recovery, and log-safety reminders.

Fresh reinstall cleanup

Destructive reset path for intentionally discarded installs.
6

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.