Skip to content

README.md

Latest commit

 

History

History
75 lines (50 loc) · 2.02 KB

README.md

File metadata and controls

75 lines (50 loc) · 2.02 KB

AX Deployment on Kubernetes

This directory contains Kubernetes manifests and configurations to deploy and verify the AX on Kubernetes using Agent Substrate.

The target Kubernetes cluster is assumed to have Agent Substrate installed.

🚀 Deploying to Agent Substrate

This option deploys AX as isolated, warm-standby actors. Workers are live-snapshotted on boot and instantly restored from GCS when a new conversation starts. Actors are automatically suspended when conversations stop emitting all of their outputs.

1. Build and Deploy

Note

Do not manually edit manifests/ax-deployment.yaml.tmpl. The installation script automatically injects your ${GEMINI_API_KEY} and ${BUCKET_NAME} environment variables during deployment.

Use the core installation script to build the images and apply the resolved manifests to your cluster:

export GEMINI_API_KEY="your-api-key"
export BUCKET_NAME="your-gcs-bucket"
./hack/install-ax.sh --deploy-ax-server

This command will:

  • Build the AX server and proxy images using ko.
  • Create the ax namespace.
  • Create the WorkerPool and ActorTemplate for AX.

Wait until the template is ready:

kubectl wait --for=condition=Ready actortemplate/ax-template -n ax --timeout=5m

2. Port-Forward Services

To interact with the router locally:

# Port-forward the Ax Router
kubectl port-forward -n ax svc/ax-router 8001:443

3. Test End-to-End

Run an execution targeting the deployed server using the external IP:

ax exec --server=localhost:8001 --input="hello"

Envoy will intercept the request and route traffic using the conversation ID.

🧹 How to Uninstall

To remove AX resources from your cluster, run:

./hack/install-ax.sh --delete-ax-server

🛠️ Inspection & Diagnostics

Use the kubectl ate CLI tool to inspect the live states of active actors and allocated standby worker pool instances:

kubectl ate get actors

kubectl ate get workers