Your first deploy

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-podinfo

In the dev environment, choose New changeset and name it add-podinfo.

Stage 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-demo

Add a change to the changeset.
Choose the podinfo source, engine helm, kind workload.
Bind it to the admiral-demo Kubernetes agent.

2. 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>

Click Plan, review the planned change, then Apply.

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>

The environment shows the component as deployed, with its Revision and run logs.

You just ran a real deployment through Admiral. The next step shows the part competitors do badly: wiring one component's output into another.

4. Wire infrastructure

Add an infra component and feed its output to this workload