Changelog

What is not ready yet?

• Applying a changeset. You can stage a changeset, have Admiral render it, and plan it. Apply is next.
• The Terraform agent. The Kubernetes agent has shipped. The Terraform agent has not.
• Hosted Terraform state. The backend at api.admiral.io, and the CLI's Terraform credentials helper, come with the Terraform agent.
• The Get Started walkthrough. Steps 1 and 2 work today. Steps 3 to 5 wait on apply and the Terraform agent.

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 publish publishes every component a repository declares in admiral.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's values.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.