Your first deploy
Deploy your first workload with Admiral: define a component in dev, stage it in a changeset, apply it through your Kubernetes agent, and watch it go live.
This is the payoff: you define a workload component in dev, stage it in a changeset, apply it, and see it running in your cluster. This deploys through your Kubernetes agent from step 1.
1. Add a workload component
A Component of kind workload deploys via the Kubernetes agent. You add it as a Change inside a changeset; you never edit an environment directly.
Open a changeset
admiral changeset create --env demo/dev --name add-podinfoStage a change that creates the component
# TODO: confirm flags - source/engine/path + target agent + values.
admiral changeset add-change <changeset> \
--name web \
--kind workload \
--source podinfo \
--engine helm \
--target admiral-demo2. Plan, review, apply
A Run has two phases. Plan first, review what will happen, then apply at the single approval gate.
admiral changeset plan <changeset>
admiral changeset apply <changeset>3. See it live
kubectl get pods --context kind-admiral-demo
# TODO: admiral-side view of the resulting Revision / run status
admiral run get <run>You just ran a real deployment through Admiral. The next step shows the part competitors do badly: wiring one component's output into another.
Next
Applications & environments
Create the resources Admiral deploys into: a source to fetch code from, an application to own it, and the dev and prod environments you promote between.
Wire infrastructure
Compose components in Admiral: add a Terraform infrastructure component, emit an output, and feed it into your workload through the dependency graph.