Before you start
- A cluster connected to Ankra and online. See Import a cluster.
- A role that may create and deploy Stacks on that cluster. Otherwise starting the draft says “Your role does not allow creating stacks on this cluster.”, and deploying says “Your role does not allow deploying this stack.”
- A Helm registry with the chart you want. Ankra’s public catalogue is there for every organisation; for your own charts, connect a Helm registry first.
- For the CLI steps, the
ankraCLI signed in to your organisation.
Create a Stack and deploy it
1
Open the cluster's Stacks
Open Infrastructure → Clusters → <your cluster>, then Stacks under Technical details in the cluster’s menu (
/next/clusters/<cluster-id>/stacks).The page lists the cluster’s Stacks under Stack inventory, with Clone stacks and Create a stack at the top.2
Start the draft
Select Create a stack. Under Start from what you already know, keep Compose a stack (add Helm add-ons and manifests yourself). The other two starts are:
- Use a stack profile - start from a versioned stack profile and answer its inputs for this cluster.
- Bring a Git definition - for a Stack already declared in the cluster’s connected GitOps repository. There is nothing to import: Ankra adds every Stack declared there on its next sync, and you open it from Stacks.
3
Add a Helm add-on
Select Add → Helm add-on. In Find a chart, search by chart name and pick the chart; the list covers every registry connected to your organisation.The dialog becomes Configure and the chart’s name. Fill in:
- Pinned chart version - an exact release. Ankra checks downgrades before it deploys.
- Add-on name - lowercase letters, digits and hyphens, unique in the Stack.
- Namespace - created by the add-on’s release if it does not exist.
- Values (optional) - starts from the release defaults. Only what you keep here is stored with the Stack.
4
Add a manifest
Select Add → Manifest. Enter a Resource name (lowercase letters, digits and hyphens) and the YAML in Manifest source. The manifest needs
apiVersion, kind and metadata.name. Select Add to draft.The manifest appears beside the add-on.5
Set the order
Select the manifest to open it in the inspector, then open its Parents tab. Under Depends on, tick the add-on: “These resources must succeed before” the manifest deploys. A choice that would loop back shows Would create a cycle and cannot be ticked.The Graph draws the manifest after the add-on, and the Table view lists the add-on under Depends on. Resources with no parents deploy first, then each one after everything it depends on.
6
Review the changes
Select Review changes. The editor switches to Changes, the Draft change log: each resource the draft installs, creates, changes or removes, with what changes.For a new Stack the confirmation reads Create and deploy this stack?: “The stack is committed to Git and its members deploy in dependency order.”
7
Deploy
Select Create and deploy stack (on a Stack that is already deployed, the button is Deploy reviewed changes).The editor reads “Deployment accepted. Follow the operation for its outcome.” Open Deployments in the editor, or the cluster’s Operations, to follow it. When the cluster has a connected GitOps repository and the Git commit is still pending, it reads “Changes accepted. Git sync is pending; check the stack before deploying again.”
Change a Stack later
Open the Stack from Stacks and select Start a draft. Everything you do from there lands in the draft, which is shared: anyone else with access can edit the same draft at the same time, and the status line shows whether your input is saved (Saving to the shared draft…, All changes saved).- Change an add-on’s values or version: select it and edit its Values tab, or its chart version in Properties. The Diff tab shows which values the Stack changes from the chart defaults.
- Change how an add-on deploys: its Deployment settings tab holds the timeout, rollback, retry and sync settings described in Add-on settings.
- Edit a manifest: its Source tab holds the YAML.
- Remove a resource: a deployed resource is staged for removal (Removal staged) and uninstalled when you deploy; a resource that exists only in the draft is removed from it.
- Add an application: Add → Application adds one of your organisation’s applications.
With the CLI
The CLI stages a Stack from an ImportCluster file as a draft, shows it and deploys it. Write the Stack into a file, for examplemy-cluster.yaml:
parents sets the order, as the Parents tab does. Paths in from_file are relative to the file. Then:
ankra cluster draft refuses a Stack that already has a draft, and stages nothing when the platform refuses any Stack in the file. The draft it stages is the same draft the stack editor opens, so you can review or edit it there before deploying. To change one add-on’s settings without a draft, use ankra cluster addons settings set.
Verify
Open Stacks on the cluster: your Stack is listed, and opening it shows the add-on and the manifest with the manifest after the add-on in the Graph. From the CLI:What can go wrong
Next steps
- Add-on settings - how an add-on is retried, rolled back and kept in sync.
- Undo a change - read a Stack’s history and restore an earlier version.
- Clone Stacks - copy a Stack to another cluster.
- Stacks - how Stacks, drafts and dependencies work.