Overview
Run a real deploy and a dev-to-prod promotion in about 20 minutes
By the end of this walkthrough you will have connected a cluster to Admiral, deployed a real workload, wired an infrastructure component to it, and promoted the whole thing from a dev environment to a production environment. All on your own machine, using a local Kubernetes cluster.
What you'll build
- An Application with two Environments:
devandprod. - A workload component deployed from a public Helm chart.
- An infrastructure component whose output feeds the workload (the dependency graph).
- A promotion that ships the same, tested setup from
devtoprod.
The path
1. Connect a cluster
Sign up, install the CLI, run an agent in a local kind cluster
2. Applications & environments
Create a source, an app, and dev + prod environments
3. Your first deploy
Deploy a workload through a changeset and watch it go live
4. Wire infrastructure
Add an infra component and pass its output to the workload
5. Promote to production
Copy the tested changeset from dev to prod
Prerequisites
Admiral is hosted, so there is no server to install. You need an account and a target to deploy into. For this walkthrough the target is a throwaway local cluster.
- An Admiral account.
- The
admiralCLI. - A local Kubernetes target, for the Kubernetes agent:
| Tool | Minimum version | Purpose |
|---|---|---|
| Docker | 20.10+ | Container runtime for kind |
| kind | 0.20+ | Local Kubernetes cluster |
| kubectl | 1.28+ | Inspect the cluster |
The agent is outbound-only - it dials api.admiral.io and pulls its work, so a local kind cluster with plain internet access is enough. No inbound networking, no port mapping. See Architecture.
A note on the two ways to drive Admiral
Every step below is shown in two tabs: the CLI and the Web, in the spirit of how a cloud provider lets you click through a UI or script the same thing. Pick whichever you prefer; they produce the same resources.