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. 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.
--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.
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>’.