Documentation Index
Fetch the complete documentation index at: https://arize-ax.mintlify.dev/docs/llms.txt
Use this file to discover all available pages before exploring further.
Overview
The diagram below depicts the target topology for Azure.
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 → network model → cluster → install → ingress → validate). Then open each linked page; 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.Choose your network model
Pick the row that matches how your cluster reaches the distribution hub and container registries. The table summarizes; the cards help you self-select quickly.
| Deployment type | Network assumption | Image source | Doc to open first |
|---|---|---|---|
| Connected | Internet egress to hub and registries | Arize AI hub by default; optional mirror to your registry | Connected summary |
| Semi-restricted | Egress only to allowlisted hosts (and Azure APIs) | Same as connected once allowlists match | Allowlist then connected flow |
| Air-gapped | Cluster isolated from Arize AI | Your private registry only | Air-gapped image-transfer paths |
Open internet to Arize AI
Use when: nodes and install host can reach
ch.hub.arize.com and image registries over HTTPS. Start here for the default Azure path.Allowlisted egress only
Use when: security requires explicit egress allowlists or a proxy. Open the same endpoints as connected, then follow the same install steps.
Isolated cluster
Use when: workloads cannot pull from the public internet. You mirror images into your registry and transfer the archive out of band.
AKS cluster and infrastructure
Bring an existing AKS cluster and supporting Azure resources in line with Arize AX, or use the Terraform modules shipped in the distribution archive to provision them.
Existing cluster
Node pools, labels, Blob Storage containers, managed identity, and storage access.
Terraform
Use bundled modules and README; align static IPs and outputs with ingress.
Install Arize AX
Configure
values.yaml for Azure and install the operator chart.Quick start
Use when: you want a complete example
values.yaml and a single Helm command to get running fast.Detailed walkthrough
Use when: you need every field explained, base64 secrets, optional mirroring, and
./arize.sh versus Helm called out step by step.Create ingress
Expose the UI and APIs with an Azure load balancer and the bundled examples, or use NGINX, Istio, Kong, or another controller with the bundled example manifests.
Azure load balancer
Static IPs,
examples/endpoints/azure, and appBaseUrl / expBaseUrl.NGINX, Istio, Kong, …
Example paths under
examples/endpoints and ingressMode guidance.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.