Get Started
Projects & environments
Create the project the walkthrough deploys into, and the dev and prod environments you deploy and promote between, each through your agent.
Now you create what Admiral deploys into: a project to own the work, and the two environments you'll deploy and promote between. Each environment deploys through the agent from step 1.
1. Create a project
admiral project create demo2. Create dev and prod environments
admiral env create demo/dev --agent demo
admiral env create demo/prod --agent demoEach environment renders into its own namespace unless you name one with --namespace: here demo-dev and demo-prod. The agent creates the namespace on the first apply.
An environment can require approvals before an apply runs, with --approvals 1, for example. Someone other than the changeset's author must then run admiral changeset approve. The walkthrough leaves approvals off, so you can finish it alone.
Check what you made with admiral env describe demo/dev. It lists the environment's agent and namespace, and later the components it runs.
Connect a cluster
Get access to Admiral, install the CLI, and run a Kubernetes agent in a kind cluster on your own machine.
Your first deploy
Deploy your first workload with Admiral: import a public Helm chart as a component, add it to dev in a changeset, plan and apply it through your Kubernetes agent, and watch it go live.