Skip to main content
This guide covers installing the Chamber agent using Helm.
For a guided setup experience, use the installation wizard in the Chamber dashboard.

​
Prerequisites

Before installing, ensure you have:
Verify with kubectl version. The agent supports Kubernetes 1.24 and later.
Verify with helm version. Install from helm.sh if needed.
Nodes must have NVIDIA drivers installed. Verify with nvidia-smi on GPU nodes.
The NVIDIA device plugin must be deployed. Verify:
kubectl get pods -n kube-system -l name=nvidia-device-plugin-ds
Get this from the Chamber dashboard (see below).

​
Quick Install

# Install the agent (OCI registry - no helm repo add needed)
helm install chamber-agent oci://public.ecr.aws/q4a1a5s3/chamber-agent-chart \
  --set clusterToken=YOUR_CLUSTER_TOKEN \
  --set clusterName=my-gpu-cluster
Your cluster will appear in the Chamber dashboard within 30 seconds.

​
Getting a Cluster Token

1

Log in to Chamber

Go to app.usechamber.io and sign in.
2

Navigate to Settings

Click Settings in the sidebar, then Cluster Tokens tab.
3

Create Token

Click Create Token, give it a name, and copy immediately.
Store your token securely. It’s only shown once and cannot be retrieved later.

​
Verifying Installation

​
Check Pod Status

kubectl get pods -l app.kubernetes.io/name=chamber-agent
Expected output: 
NAME                              READY   STATUS    RESTARTS   AGE
chamber-agent-5d4f6b7c8d-abc12    1/1     Running   0          30s

​
Check Logs

kubectl logs -l app.kubernetes.io/name=chamber-agent --tail=20
Look for: 
INFO  Connected to Chamber control plane
INFO  Discovered 4 GPU nodes with 32 total GPUs

​
Verify in Dashboard

Within 30 seconds of installation:
  1. Go to app.usechamber.io
  2. Navigate to Capacity Pools
  3. Your cluster should appear with the correct GPU count
If GPUs show as 0, verify the NVIDIA device plugin is running and nodes have nvidia.com/gpu resources.

​
Network Requirements

The agent requires outbound HTTPS access to:
HostPortPurpose
controlplane-api.usechamber.io443Control plane communication
The agent only makes outbound connections. No inbound firewall rules are required.

​
Uninstalling

helm uninstall chamber-agent
Uninstalling disconnects your cluster from Chamber. Running jobs will continue to completion but won’t be tracked.

​
Next Steps

Troubleshooting

Common issues and solutions

Upgrading

Upgrade to the latest version