What's New
Changelog
What has shipped in Admiral, by month, newest first.
What is not ready yet?
- Terraform and Kubernetes components in one changeset. A changeset holds one kind today, so a Terraform output can't yet feed a workload's values. Terraform components can already read each other's outputs.
- A promote action. To ship from
devtoprod, repeat the change inprod, as Promote to production shows. - Signing in from CI as a service account. CI uses a personal API key today, see Access.
- Step 4 of the Get Started walkthrough, wiring infrastructure. The other steps work.
November 2026
November renamed Admiral's nouns, connected it to GitHub, and made the way out of a failed apply work.
- Organization and project. Tenant is now organization and application is now project, in the API, the CLI, the console and the Terraform provider, which ships
admiral_project. Ids startorg-andprj-. - GitHub. Admiral's GitHub App connects an organization's repositories:
- A push publishes the components a repository's
admiral.yamldeclares. - A pull request is planned in the environments that track its base branch, and carries one Admiral check and one comment. When the merge publishes the same bytes, its approved plan applies, unless the environment's
--after-mergesays to wait for a person. - An environment can track a branch, a tag pattern or a version range.
- A push publishes the components a repository's
- Sources. A source is one upstream location with a standing grant. Import a component through it, and browse what it offers.
- Outputs between Terraform components. A Terraform component's value can reference another Terraform component's output in the same changeset. Admiral resolves it at plan time, or defers the consumer until the apply knows it.
- The way out of a failed apply:
- An apply that left something unwritten holds its environment. You apply it again, edit it in place, or revert it in place, by component. Accepting what landed is break-glass for an organization admin.
- An apply that wrote everything but left a component unhealthy holds nothing.
- A failure stops only what depends on it, and an apply that never reported reads unknown.
- The Kubernetes agent's health wait:
- It ends at once where waiting can't help, including an image that doesn't exist.
- While it waits, it shows restart counts, Warning events, and a crashed container's last 20 lines.
- A plan names every Role the agent may not create, in one pass.
- Agents can be limited to an allowed list of components.
- CLI.
admiral changeset rebasebrings a changeset that fell behind up to date, andadmiral changeset values --effectiveshows every value a component will receive and where it came from.
October 2026
October shipped apply and Terraform, so a changeset goes from a plan to a change in your cluster or cloud.
- Apply. A changeset is planned, approved where its environment requires approvals, and applied. The apply runs exactly the plan that was reviewed.
- Terraform and OpenTofu. Terraform components plan and apply on an infra agent that runs in your account. An environment sets the engine version and the state backend.
- Hosted Terraform state. Admiral can keep each component's state.
admiral state versionsandadmiral state downloadread its history. - Agents.
admiral agent createtakes a kind and prints the install. An agent signs in as its own service account, with a single-use enrollment key the first time. - The Kubernetes agent:
- It takes over fields from Argo CD, Flux, Pulumi, Terraform, Helm and kubectl when an approved plan says so.
- It can pause an object, and judge health its own way with
admiral.io/healthy-when. - It elects one leader among its pods, and exports JSON logs and Prometheus metrics.
- Sealed at rest. Plan files, run artifacts and outputs are encrypted at rest.
- CLI. The deploy loop needs no ids:
changeset plan,approveandapplytakeproject/environment.--fullshows each changed resource whole, andadmiral apikeymanages your keys.
September 2026
September added the component registry, changesets, and the Kubernetes agent, so a team can publish a component, stage it in an environment, and have its cluster's agent plan it.
- Component registry.
admiral component publishpublishes every component a repository declares inadmiral.yaml. A registry pull copies a module or chart you do not own, using a stored credential when the source is private. Revisions are content-addressed and labeled by tags, and a revision can be deprecated or revoked after it is published. Each revision records its inputs, with each input's validation, whether it accepts null, and a chart'svalues.schema.json. - Changesets. Stage changes to one environment, have Admiral render them, read what it rendered, and plan them with the environment's agent.
- Kubernetes agent. Admiral trusts a cluster through its service-account token issuer or keys you upload, with no shared secret. An agent can be granted to an organization, a team, an application, or one environment.
- Organizations and access. Environments, invitations, and personal and service account API keys. A key stops working when its owner leaves the organization.
- Tools. The CLI covers applications, environments, components, credentials, and changesets. The Terraform provider adds
admiral_environment.