ankra stack-profiles
Manage organisation-level stack profiles: create them from deployed stacks, list and describe them, apply them to clusters, version and share them, and export or import them as infrastructure-as-code.ankra stack-profiles adopt
Record an already-deployed stack as a tracked deployment of a stack profile. Capturing a profile from a live stack (‘create--stack’, ‘save-version
--stack’) snapshots the contents but does not register the source stack as a
deployment, so the profile reports no deployments and ‘rollout’ cannot reach
it. Adopt writes that missing record.
Nothing is written to the cluster: no draft, no deploy, no change to the
stack or its members. Only the deployment record appears, after which
‘deployments’ lists the stack and ‘rollout’ can update it in place.
Adopt reports how the live stack differs from the version it is adopted at
rather than refusing a stack that has drifted - a stack patched per cluster
since capture has drifted by definition, and that is the case adopt exists
for. Read the report before rolling out: a rollout replaces the stack with
what the version lists, so any member listed under “only on the cluster” is
removed by it once you confirm it with --confirm-removal (the platform refuses
the rollout until you do). Pick the version that matches with --version, or publish a
version that carries those members first.
ankra stack-profiles apply
Apply (instantiate) a stack profile onto a cluster. By default this creates a reviewable stack DRAFT on the target cluster - nothing is deployed until you review it in the Ankra dashboard or pass--deploy.
Repeat --cluster to apply the same version and bindings to several clusters in
one command; a summary table reports each cluster at the end.
Bind profile parameters with --set name=value. For secret parameters prefer
--set-file name=path or --set-env name=ENV_VAR so the value never appears in your
shell history or process list. Use ‘ankra stack-profiles get <profile-id>’ to see
which parameters a profile expects.
ankra stack-profiles contents
Show what a published profile version actually contains. Manifests and add-on values are stored base64-encoded, soexport-iac and
version cannot be read or grepped directly. This command decodes them.
With no --resource, it lists the add-ons and manifests, reading each
manifest’s kind and namespace out of the decoded YAML:
--resource prints one resource’s decoded content, the same way
ankra cluster manifests get prints a live manifest:
--all prints every resource as one multi-document YAML stream, which is the
form to audit a whole profile in one pass:
ankra stack-profiles create
Create a stack profile by snapshotting a deployed cluster stack as version 1. The source stack’s add-ons and manifests become the profile contents; detected inputs become the profile’s parameters.ankra stack-profiles delete
Delete a stack profile. Stacks already deployed from it keep running; the profile stops appearing in the catalogue and can no longer be applied.ankra stack-profiles demo
Launch a demo of a profile on the staging cluster to see what it actually installs - no cluster of your own required. A demo installs the profile’s add-ons and manifests into one throwaway namespace, quota-bounded so it cannot crowd the staging cluster, and cleans itself up automatically.ankra stack-profiles demo detail
Show a demo’s workloads and readinessankra stack-profiles demo launch
Launch a demo of a profile on the staging clusterankra stack-profiles demo list
List the live demos of a profileankra stack-profiles demo logs
Read a demo’s pod logsankra stack-profiles demo stop
Stop a demo and clean up its namespaceankra stack-profiles deployments
List every stack your organisation deployed from this profile: the target cluster, the stack, the profile version it runs, and whether a newer version is available.--outdated keeps only the ones behind the current
version; -o json returns the raw records.
ankra stack-profiles deprecate
Withdraw a published version so nobody deploys it again. A deprecated version cannot be made current and cannot be applied to a cluster; stacks already running it keep running, and ‘ankra stack-profiles deployments’ reports which ones are on it. The reason is one of incompatibility, critical-bug or cve. Use--note for
the sentence the platform shows when it refuses the version, such as which
version carries the fix, and repeat --reference for the advisories, CVE ids
or issues behind it. Deprecating an already-deprecated version replaces its
reason, note and references.
ankra stack-profiles diff
Compare two published versions of a profileankra stack-profiles drafts
Work with stack profile builder drafts from the terminal. A draft is the editable working copy behind a profile version: open one from an existing profile (or from a deployed stack), annotate its parameters with the titles and descriptions the launch form shows as guidance, and publish it as the next version.ankra stack-profiles drafts annotate
Set a parameter’s title and description on a draft. The description is the guidance the launch form shows under the field, so this is how a profile author instructs the person filling it in. Publishing the draft makes the annotations live.ankra stack-profiles drafts create
Open a builder draft:--profile edits an existing profile (publishing
creates its next version), --name starts a brand-new profile, and
--source-cluster with --source-stack seeds the draft from a deployed stack.
ankra stack-profiles drafts delete
Discard a builder draftankra stack-profiles drafts get
Show a draft’s parameters and their annotationsankra stack-profiles drafts list
List the organisation’s open builder draftsankra stack-profiles drafts options
Give a draft’s input choices, where each choice also answers other inputs. One “Model size” input with a choice of 8b or 32b can then move the model id, the context length and the volume size together, so whoever applies the profile picks one thing instead of keeping four consistent. At apply time the platform resolves a choice in a fixed order: a value passed with--set, then
what the selected choice sets, then the input’s own default.
A choice can set any non-secret input that does not offer choices of its own.
Declare a choice input that no manifest references with
‘drafts annotate <draft-id> --parameter <name> --add --type enum’.
ankra stack-profiles drafts options remove
Remove one choice from an inputankra stack-profiles drafts options set
Add or update one choice on an inputankra stack-profiles drafts publish
Publish a draft as a profile versionankra stack-profiles drafts rebase
Move a draft’s base to the profile’s latest published version. A draft opened before someone else published cannot be published until it is rebased; the draft’s contents are kept and the upstream changes reported.ankra stack-profiles drafts submit-suggestion
Submit a draft that edits another organisation’s public profile as a suggestion. The owning organisation reviews it with ‘ankra stack-profiles suggestions’; submitting retires the draft.ankra stack-profiles drafts validate
Run the publish validations on a draft without publishingankra stack-profiles export-iac
Export a profile version as ClusterInfrastructureAsCode YAMLankra stack-profiles get
Describe a stack profile: its metadata, published versions, and the parameters you can bind when applying it.ankra stack-profiles import
Import a ClusterInfrastructureAsCode YAML file as a stack profile, publishing its first version immediately. With--as-draft the document opens as a builder draft instead, so a file-authored candidate can be reviewed before anything is published: when your organisation already has a profile with the document’s name (or the --name override) the draft attaches to it as the next-version candidate, and otherwise it opens as a new-profile draft. Review it with ‘ankra stack-profiles drafts validate’ and ship it with ‘ankra stack-profiles drafts publish’.
ankra stack-profiles list
List stack profiles in the active organisationankra stack-profiles logo
Manage the uploaded logo a profile shows in the catalogue. Uploading stores the image bytes with Ankra and clears any logo URL; to reference an image by URL instead, use ‘ankra stack-profiles update--logo-url’.
ankra stack-profiles logo clear
Remove a profile’s uploaded logoankra stack-profiles logo get
Download the uploaded logo’s image bytes. Without--output the file is
named after the profile reference with the served image type’s extension.
ankra stack-profiles logo set
Upload a logo image for a profile you own. PNG, JPEG, and WebP are accepted, at most 512 KiB; large images are resized automatically and square images look best. The upload clears any stored logo URL.ankra stack-profiles rollout
Update the stacks deployed from a profile to a published version, in place. For every target the platform replaces the contents of the stack that deployment already runs with the chosen version - the same stack, so Kubernetes performs a rolling update of the workloads and nothing is created twice - and records the deployment at the new version, so ‘deployments’ and the profile’s fleet view read up to date. The non-secret inputs each deployment was last applied with are carried forward; bind new values or secret inputs with--set, --set-file and --set-env, exactly as for apply.
Pick targets with --cluster (repeatable) or --all for every deployment of the
profile; add --outdated to touch only the ones behind the chosen version.
Without --version the profile’s current version is rolled out.
A member of a target stack that the version does not list is removed. The
platform does that without asking only for a member it can show this profile
put there; any other removal (an add-on, manifest or application someone added
to the stack) is refused, with nothing changed, unless you name it with
--confirm-removal cluster:kind/name (a confirmation is for that cluster’s
stack only; with a single target the cluster may be left out). --dry-run lists, per stack, the members the
version would remove, and writes nothing. A rollout to more than one stack
asks first (--yes skips the question), and it stops at the first stack that
fails (--continue-on-error keeps going).
--via-apply uses the older path instead: the version is exported as
ClusterInfrastructureAsCode and applied with the cluster apply lane. It
updates the stack the same way but leaves the fleet view at the previous
version; use it only against a platform that predates in-place upgrades. That
lane cannot tell whose a member is, so it refuses every removal you do not
name with --confirm-removal.
The write returns as soon as the platform has accepted it; the manifest and
add-on deploys run in the background. Watch them with
‘ankra cluster operations list --cluster <name>’.
ankra stack-profiles save-version
Save a new profile version by re-snapshotting a deployed stack. The new version becomes the profile’s current version.ankra stack-profiles set-current-version
Set which published version new deployments of this profile resolve to. Rolling back is setting the pointer to an earlier version.ankra stack-profiles share
Share a profile with specific organisations. Shared organisations can view and deploy every version but cannot change the profile. Ask the other organisation for their slug - admins find it under organisation settings.ankra stack-profiles share add
Share a profile with another organisationankra stack-profiles share list
List the organisations a profile is shared withankra stack-profiles share remove
Revoke one share grant by its id (from ‘share list’). The organisation loses access to the profile; stacks it already deployed keep running.ankra stack-profiles suggestions
Review the cross-organisation suggestions submitted against a profile. Approving one publishes its frozen contents as the profile’s next version. Withdraw is the proposer’s verb for a suggestion their organisation submitted.ankra stack-profiles suggestions approve
Approve a suggestion, publishing it as the profile’s next versionankra stack-profiles suggestions get
Show one suggestion’s contents and upstream driftankra stack-profiles suggestions list
List the suggestions visible to your organisation on a profileankra stack-profiles suggestions reject
Reject a suggestion, optionally with a note the proposer can readankra stack-profiles suggestions withdraw
Withdraw a suggestion your organisation submittedankra stack-profiles summary
Read the reviewed summary of an exact profile version, inspect its selected evidence, review an existing candidate, or withdraw an approval. Use status, generate and policy for explicit generation controls. No operation changes a workload version. The platform checks current permissions and source visibility on every request. Read the candidate and its source_revision, candidate_revision and summary_revision before deciding. Supply those exact counters; do not fetch newer counters and retry a stale decision automatically. After an uncertain write, read back before retrying. Output is JSON by default; use -o yaml for YAML.ankra stack-profiles summary cancel
Cancel one generation without withdrawing an approvalankra stack-profiles summary draft-status
Read generation and approval state for the draft revision you inspectedankra stack-profiles summary edit
Select existing facts for an unapproved candidateankra stack-profiles summary evidence
Inspect evidence selected by the current approvalankra stack-profiles summary generate
Request one private candidate. The platform must have generation enabled, a configured model, current organisation consent and sufficient budget. This command grants none of those prerequisites and does not publish a summary or change a workload. First read status (or draft-status). Create and save a request-key before admission. Supply the exact source and summary revisions you inspected, including summary revision zero. After an uncertain response, retry with the SAME key, source and revisions. Do not create a new key or refresh expectations for that retry. The server rejects conflicting reuse. Inspect generation <id> for progress and review separately.ankra stack-profiles summary generate-draft
Request one private candidate. The platform must have generation enabled, a configured model, current organisation consent and sufficient budget. This command grants none of those prerequisites and does not publish a summary or change a workload. First read status (or draft-status). Create and save a request-key before admission. Supply the exact source and summary revisions you inspected, including summary revision zero. After an uncertain response, retry with the SAME key, source and revisions. Do not create a new key or refresh expectations for that retry. The server rejects conflicting reuse. Inspect generation <id> for progress and review separately.ankra stack-profiles summary generation
Inspect a private candidate and its revision countersankra stack-profiles summary get
Read one version’s approved summaryankra stack-profiles summary policy
Read policy get first: inspect the data-use notice, provider destination, provider terms, consent digest and current policy revision. Approval requires a human identity with ai.manage and explicit limits and acknowledgements. It does not enable generation or select a model. After an uncertain policy write, read back before deciding what to do next.ankra stack-profiles summary policy approve
Read policy get first: inspect the data-use notice, provider destination, provider terms, consent digest and current policy revision. Approval requires a human identity with ai.manage and explicit limits and acknowledgements. It does not enable generation or select a model. After an uncertain policy write, read back before deciding what to do next. To change OpenRouter routing, preview with policy get--openrouter-ingress europe
--openrouter-upstream google-vertex/europe. Review the returned destination and
consent_digest, then supply the SAME routing flags and that digest to approve.
The preview makes no changes. Omit both flags to retain saved routing.
Europe requires regional access under your OpenRouter agreement; the option alone
does not establish data residency. Requests require zero retention, no data
collection and no provider fallback. These commands do not verify your contract.
ankra stack-profiles summary policy get
Read policy get first: inspect the data-use notice, provider destination, provider terms, consent digest and current policy revision. Approval requires a human identity with ai.manage and explicit limits and acknowledgements. It does not enable generation or select a model. After an uncertain policy write, read back before deciding what to do next. To change OpenRouter routing, preview with policy get--openrouter-ingress europe
--openrouter-upstream google-vertex/europe. Review the returned destination and
consent_digest, then supply the SAME routing flags and that digest to approve.
The preview makes no changes. Omit both flags to retain saved routing.
Europe requires regional access under your OpenRouter agreement; the option alone
does not establish data residency. Requests require zero retention, no data
collection and no provider fallback. These commands do not verify your contract.
ankra stack-profiles summary policy revoke
Revoke the exact consent revision you inspectedankra stack-profiles summary request-key
Create a request key locally. Save it before submitting generation. This command does not contact the platform. Never create a new key to retry an uncertain request.ankra stack-profiles summary review
Approve or reject the exact candidate you inspected. Approval requires a human identity; service and board principals are refused. For a version, approval publishes its summary. Draft approvals remain private. Workload versions do not change.ankra stack-profiles summary runtime-qualification
Run fixed synthetic checks on the organisation’s configured staging cluster and approved candidate image. Requires ai.manage and cluster read access; start and cancel also require clusters.operate. No profile content or model request is sent. A completed report can contain violated and unverified checks. These operations do not issue an admission receipt, enable generation or change consent.ankra stack-profiles summary runtime-qualification cancel
Run fixed synthetic checks on the organisation’s configured staging cluster and approved candidate image. Requires ai.manage and cluster read access; start and cancel also require clusters.operate. No profile content or model request is sent. A completed report can contain violated and unverified checks. These operations do not issue an admission receipt, enable generation or change consent.ankra stack-profiles summary runtime-qualification get
Run fixed synthetic checks on the organisation’s configured staging cluster and approved candidate image. Requires ai.manage and cluster read access; start and cancel also require clusters.operate. No profile content or model request is sent. A completed report can contain violated and unverified checks. These operations do not issue an admission receipt, enable generation or change consent.--wait exits 0 when a report is collected, even if observations are violated or
unverified; inspect report.checks before deciding what it proves. Failed, cancelled
or interrupted operations exit 1. Timeout exits 5. Interrupting the wait does not
cancel the remote operation; use cancel explicitly. Without --wait, exit 0 means
the operation was read or accepted. JSON/YAML stdout contains one response only.
ankra stack-profiles summary runtime-qualification start
Run fixed synthetic checks on the organisation’s configured staging cluster and approved candidate image. Requires ai.manage and cluster read access; start and cancel also require clusters.operate. No profile content or model request is sent. A completed report can contain violated and unverified checks. These operations do not issue an admission receipt, enable generation or change consent. The request ID is printed to stderr before sending. Save it. If the response is uncertain, repeat start with the SAME--request-id and organisation; never use a
new ID to recover an existing request. A replay returns the recorded operation.
--wait exits 0 when a report is collected, even if observations are violated or
unverified; inspect report.checks before deciding what it proves. Failed, cancelled
or interrupted operations exit 1. Timeout exits 5. Interrupting the wait does not
cancel the remote operation; use cancel explicitly. Without --wait, exit 0 means
the operation was read or accepted. JSON/YAML stdout contains one response only.