## 1. Decide where jobs will actually run
Pick one:
### Option A — Kubernetes / cluster setup
Use this if you want shared GPU/CPU infrastructure and a
persistent Launch agent.
Recommended for “real” team usage.
### Option B — Local Docker setup
Use this if you want jobs to run on your own machine,
e.g. local workstation with Docker and possibly a GPU.
Good for testing Launch quickly.
I’d usually start with **Kubernetes** if
you have cluster access. If not, start with **Local Docker**.
## 2. Create a Launch queue in the W&B UI
Go to the Launch page for the entity: https://wandb.ai/wandb/launch
Then:
1. Click **Create Queue**.
2. Select entity: `wandb`.
3. Give the queue a name.
4. Choose the queue resource type:
- **Kubernetes** for cluster execution.
- **Docker** for local execution.
5. Add the queue resource configuration.
6. Click **Create Queue**.
## 3. Kubernetes path: install a Launch agent with Helm
If using Kubernetes, you need:
- A Kubernetes cluster.
- `kubectl` access to the cluster.
- `helm` installed locally.
- A W&B **service account API key**.
- Permission to create/update/delete Kubernetes resources in the target namespace.
Do **not** use your personal API key for the agent if this is a real
setup. Use a W&B service account key.
