Skip to main content

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.

​
Summary

Use this path when your install host can reach the distribution hub at ch.hub.arize.com and your cluster can pull container images from Arize’s registries over the internet. ch.hub.arize.com covers distribution metadata and JWT-authenticated downloads; us-central1-docker.pkg.dev hosts the container images the chart pulls by default. Mirroring images into your own registry is optional unless policy requires it.

​
Network and images

  • Distribution: Download with your JWT from ch.hub.arize.com as described in Download and extract the distribution.
  • Images: By default, workloads pull using the chart’s pullRegistry (defaults align with Arize’s hub and Google Artifact Registry hosting for AX images—see your release’s Advanced → Helm for the exact strings).
  • Telemetry (Call Home): Defaults keep optional hub connectivity for platform alerts and metrics. Anything other than the defaults—including compliance-driven restrictions—is documented only under Advanced → Helm in the offline docs/ bundle from your distribution archive (open docs/index.html locally).

​
Firewall and script checks

When you run ./arize.sh operations that pull from the hub, the script may verify HTTPS reachability to ch.hub.arize.com and us-central1-docker.pkg.dev. If a step fails with a connectivity error, allowlist both endpoints (see Semi-restricted) or ask your network team to open them for the install host.

​
Private registry mirror

If policy still requires every workload image to live in your Artifact Registry or Container Registry—even though nodes have internet egress—mirror first, then point pullRegistry / pushRegistry at your hostname in values.yaml (see the detailed walkthrough (GCP)).
  1. Authenticate Docker (gcloud auth configure-docker or your registry’s login flow).
  2. Run ./arize.sh to pull from the Arize hub and push into your registry. Pass hubJwt as the base64-encoded JWT Arize gave you, cloud=gcp, and pushRegistry set to your registry endpoint: 
    ./arize.sh -f none -y load-remote-images 'hubJwt=<BASE64_JWT>,cloud=gcp,pushRegistry=<YOUR_REGISTRY>'
  3. Example hostnames (replace project, location, and repository): us-central1-docker.pkg.dev/<project>/<repository> for Artifact Registry, or gcr.io/<project-id> for legacy Container Registry.
  4. Verify images exist in your registry before helm upgrade --install.
If no single host can reach both the public hub and your private registry and the cluster (common in split networks), use the workflows on Air-gapped instead of this page’s mirror shortcut.

​
Next steps

  1. Provision or use a GKE cluster (or Terraform).
  2. Install Arize (quick start) or detailed walkthrough for operator values and ./arize.sh.
  3. Configure ingress or another controller.
  4. Validate the deployment.