ankra cluster

Commands for managing and operating on clusters. Flags

Flag	Default	Description
`--cluster`		Target cluster name or ID for this command, overriding `ankra cluster select`

ankra cluster access

List, grant, and revoke per-user access to a cluster’s Kubernetes API through the Ankra gateway (the access used by ‘ankra cluster kubeconfig’ and ‘ankra cluster kube-token’). Managing access requires organisation admin rights. Grants apply to one cluster and one organisation member, identified by email. Examples: ankra cluster access list —cluster my-cluster ankra cluster access grant [email protected] —cluster my-cluster —role view ankra cluster access grant [email protected] —cluster my-cluster —role edit —namespace staging ankra cluster access revoke [email protected] —cluster my-cluster ankra cluster access revoke 6f1f9aca-2c3d-4e5f-8a9b-0c1d2e3f4a5b —cluster my-cluster

ankra cluster access grant

Grant an organisation member access to a cluster’s Kubernetes API through the Ankra gateway. The grant is cluster-wide by default; pass —namespace to limit it to one namespace. Roles map to the standard Kubernetes ClusterRoles: view, edit, admin, cluster-admin.

ankra cluster access grant <email> [flags]

Flags

Flag	Default	Description
`--cluster`		Cluster name or ID (defaults to the selected cluster)
`--namespace`		Limit the grant to one namespace (default: cluster-wide)
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--role`	`view`	Kubernetes role for the grant: view, edit, admin, or cluster-admin

ankra cluster access list

List access grants for a cluster

ankra cluster access list [flags]

Flags

Flag	Default	Description
`--cluster`		Cluster name or ID (defaults to the selected cluster)
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster access revoke

Revoke gateway access from a cluster. Pass a grant ID (from ‘ankra cluster access list’) to revoke a single grant, or an email address to revoke every grant that member has on the cluster.

ankra cluster access revoke <grant-id|email> [flags]

Flags

Flag	Default	Description
`--cluster`		Cluster name or ID (defaults to the selected cluster)

ankra cluster addons

Commands to list, manage settings, and uninstall addons.

ankra cluster addons available

List addons available for installation

ankra cluster addons available [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster addons list

List addons for the active cluster; or show details for a single addon

ankra cluster addons list [addon name] [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster addons settings

Get settings for an addon

ankra cluster addons settings <addon_name> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster addons uninstall

Uninstall an addon from the cluster

ankra cluster addons uninstall <addon_name> [flags]

Flags

Flag	Default	Description
`--delete`	`false`	Also delete the addon permanently
`--yes`	`false`	Skip the confirmation prompt

ankra cluster addons update

Update addon settings by providing a JSON file that conforms to the settings schema. Example JSON file: { “retry_policy”: { “limit”: 3, “backoff”: { “duration”: “5s”, “factor”: 2, “max_duration”: “3m” } }, “sync_policy”: { “automated”: true, “self_heal”: true, “auto_prune”: false }, “revision_history_limit”: 10 } Usage: ankra cluster addons update my-addon -f settings.json

ankra cluster addons update <addon_name> [flags]

Flags

Flag	Default	Description
`-f`, `--file`		Path to JSON settings file (required)

ankra cluster addons upgrade

Upgrade an addon by patching just the fields you supply. At least one mutating flag is required. Examples:

Bump chart version

ankra cluster addons upgrade ankra-website —chart-version 1.0.146
—cluster website-demo

Tweak a single Helm values field with —set (mutates the existing values)

ankra cluster addons upgrade website —set image.tag=1.0.146
—cluster website-demo

Address a list item by a field instead of an index

ankra cluster addons upgrade website —set ‘env[name=LOG_LEVEL].value=debug’
—cluster website-demo

Replace the whole values document

ankra cluster addons upgrade website
—values-from-file ./values.yaml —cluster website-demo —set* and —values-from-file are mutually exclusive: —set* mutates the existing values document while —values-from-file replaces it. Changing —namespace is destructive (Helm reinstall in the new namespace, leaves the old release orphaned). Use —yes to skip the confirmation prompt or interactively confirm.

ankra cluster addons upgrade <addon_name> [flags]

Flags

Flag	Default	Description
`--add-parent`	`[]`	Add a dependency parent, e.g. —add-parent name=infisical-ns,kind=manifest (kind defaults to manifest; repeatable)
`--chart-version`		New chart version to install
`--cluster`		Target cluster (name or ID); defaults to the active selection
`--dry-run`	`false`	Print the proposed before/after spec without applying changes
`--namespace`		Change the addon’s namespace (destructive: Helm reinstall)
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--registry-credential-name`		New helm registry credential name
`--registry-name`		New helm registry name
`--registry-url`		New helm registry URL
`--remove-parent`	`[]`	Remove a dependency parent, e.g. —remove-parent name=infisical-ns,kind=manifest (repeatable)
`--set`	`[]`	Helm-style values mutation, e.g. —set image.tag=1.0.0 (MUTATES existing values; repeatable, comma-separated)
`--set-file`	`[]`	Like —set but reads the value from a file: key=path or key=@path
`--set-parent`	`[]`	Replace ALL dependency parents with the given set (repeatable); pass none with the others to clear
`--set-string`	`[]`	Like —set but always treats the value as a string
`--stack`		Stack name (required when the addon exists in multiple stacks)
`--values`		Use `-` to read values YAML from stdin (REPLACES the entire values document)
`--values-from-file`		Path to YAML values file (REPLACES the entire values document)
`--yes`	`false`	Skip the confirmation prompt for destructive changes (—namespace)

ankra cluster addons values

Print the current Helm values document for an addon. By default the decoded YAML is written to stdout, making it easy to pipe into a file or edit and re-apply with —values-from-file: ankra cluster addons values my-addon > values.yaml ankra cluster addons values my-addon -o raw # base64-encoded form

ankra cluster addons values <addon_name> [flags]

Flags

Flag	Default	Description
`--cluster`		Target cluster (name or ID); defaults to the active selection
`-o`, `--output`		Output format: yaml (decoded, default) or raw (base64)

ankra cluster agent

Commands to view agent status, get tokens, and upgrade agents.

ankra cluster agent status

Get agent status for the selected cluster

ankra cluster agent status [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster agent token

Get or generate agent token for the selected cluster

ankra cluster agent token [flags]

Flags

Flag	Default	Description
`--generate`	`false`	Generate a new agent token
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster agent upgrade

Upgrade the agent on the selected cluster

ankra cluster agent upgrade

ankra cluster apply

Apply an ImportCluster YAML to the Ankra API

ankra cluster apply [flags]

Flags

Flag	Default	Description
`--allow-repoint`	`false`	Allow this apply to change the cluster’s GitOps repository or branch. Resources the new source does not define are pruned
`--allow-repoint-destroying-data`	`false`	Additionally allow a repoint on a cluster holding PersistentVolumeClaims, whose data the prune destroys. Requires —allow-repoint
`--dry-run`	`false`	Validate the ImportCluster YAML locally without calling the API
`-f`, `--file`		Path to the ImportCluster YAML file to apply
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--timeout`	`10m0s`	Maximum time to wait when —wait is set
`--wait`	`false`	Wait for the configuration write to be applied and report its result. Add-on deploys are dispatched afterwards and are NOT covered by this flag - watch them with ‘ankra cluster operations list’

ankra cluster clear

Clear the active cluster selection

ankra cluster clear

ankra cluster clone

Clone stacks from an existing cluster ImportCluster YAML to a new cluster. The source can be either a local file path or a URL (http/https). Examples: ankra cluster clone cluster.yaml new-cluster.yaml ankra cluster clone https://github.com/user/repo/raw/main/cluster.yaml new-cluster.yaml ankra cluster clone cluster.yaml new-cluster.yaml —stack “monitoring” —stack “networking” Flags: —clean: Replace all stacks in the new cluster with those from the existing cluster —force: Force merge even when stack/addon/manifest names conflict —copy-missing: Copy missing files even for skipped stacks —stack: Clone only specific stacks by name (can be used multiple times) Without flags: Merge stacks, skipping any with conflicting names

ankra cluster clone <existing_cluster_file_or_url> <new_cluster_path> [flags]

Flags

Flag	Default	Description
`--clean`	`false`	Replace all stacks in the new cluster
`--copy-missing`	`false`	Copy missing files even for skipped stacks
`--force`	`false`	Force merge even when names conflict
`--stack`	`[]`	Clone only specific stacks by name (can be used multiple times)

ankra cluster decrypt

Decrypt SOPS-encrypted values stored on a cluster or in a local cluster.yaml.

ankra cluster decrypt addon

Decrypt a SOPS-encrypted addon’s Helm values and print the result to stdout. Two modes: Cluster mode (default): fetch the addon values from a live cluster, decrypt, and print to stdout. File mode (-f cluster.yaml): read the addon values file referenced from a local cluster.yaml, decrypt, and print to stdout. Examples: ankra cluster decrypt addon —name grafana ankra cluster decrypt addon —name grafana —cluster prod —stack monitoring ankra cluster decrypt addon —name grafana -f cluster.yaml

ankra cluster decrypt addon [flags]

Flags

Flag	Default	Description
`--cluster`		Target cluster (name or ID); defaults to the active selection (cluster mode)
`-f`, `--file`		Path to a local cluster YAML (enables file mode)
`--name`		Name of the addon (required)
`--stack`		Stack name (cluster mode; required when the addon exists in multiple stacks)

ankra cluster decrypt manifest

Decrypt a SOPS-encrypted manifest and print the result to stdout. Two modes: Cluster mode (default): fetch the manifest from a live cluster, decrypt it, and print to stdout. File mode (-f cluster.yaml): read the manifest file referenced from a local cluster.yaml, decrypt it, and print to stdout. Examples:

Cluster mode against the selected cluster

ankra cluster decrypt manifest db-secret

Cluster mode against a specific cluster

ankra cluster decrypt manifest db-secret —cluster prod

File mode

ankra cluster decrypt manifest db-secret -f cluster.yaml

ankra cluster decrypt manifest <manifest_name> [flags]

Flags

Flag	Default	Description
`--cluster`		Target cluster (name or ID); defaults to the active selection (cluster mode)
`-f`, `--file`		Path to a local cluster YAML (enables file mode)

ankra cluster deprovision

Stop a running managed cluster. This will shut down the cluster but not delete it. If no cluster name is provided, uses the currently selected cluster. For cloud clusters (hetzner, ovh, upcloud, digitalocean, proxmox, morpheus) this command routes to the provider-specific deprovision endpoint so cloud resources are released.

ankra cluster deprovision [cluster_name] [flags]

Flags

Flag	Default	Description
`--force`	`false`	Force deprovision even if cluster is in an unexpected state; on UpCloud, Hetzner, OVH and DigitalOcean also deletes leftover CSI storage volumes and load balancers
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--yes`	`false`	Skip the confirmation prompt

ankra cluster digitalocean

Commands to create, deprovision, and scale DigitalOcean clusters.

ankra cluster digitalocean bastion

Resize the cluster’s single bastion/gateway node. Find its node ID with ‘nodes list’.

ankra cluster digitalocean bastion resize

Resize the bastion/gateway node. The provider’s bastion/gateway update job powers it off, resizes it, and powers it back on, causing brief SSH/NAT downtime for the cluster.

ankra cluster digitalocean bastion resize <cluster_id> <instance_type> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--timeout`	`10m0s`	Maximum time to wait when —wait is set
`--wait`	`false`	Wait for the operation to finish and report success or failure (default: submit and return immediately)

ankra cluster digitalocean control-plane

Inspect and change the control plane configuration. The cluster must be stopped to change the controller count or instance type. Only 1 or 3 controllers are allowed (etcd needs an odd number of voting members for quorum). Changes apply the next time the cluster is started.

ankra cluster digitalocean control-plane get

Show the current control plane configuration

ankra cluster digitalocean control-plane get <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster digitalocean control-plane set-count

Change the controller count (1 or 3)

ankra cluster digitalocean control-plane set-count <cluster_id> <count> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster digitalocean control-plane set-instance-type

Change the controller instance type

ankra cluster digitalocean control-plane set-instance-type <cluster_id> <instance_type> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster digitalocean create

Create a new DigitalOcean cluster

ankra cluster digitalocean create [flags]

Flags

Flag	Default	Description
`--bastion-size`	`s-1vcpu-1gb`	Bastion droplet size
`--control-plane-count`	`1`	Number of control plane nodes
`--control-plane-size`	`s-2vcpu-4gb`	Control plane droplet size
`--credential-id`		DigitalOcean API credential ID (required)
`--distribution`	`k3s`	Kubernetes distribution: k3s or kubeadm
`--etcd-node-count`	`3`	Number of dedicated etcd nodes when —etcd-topology=external (3 or 5)
`--etcd-size`	`s-2vcpu-4gb`	Droplet size for dedicated etcd nodes when —etcd-topology=external
`--etcd-topology`	`stacked`	etcd topology for kubeadm clusters: stacked (on control plane) or external (dedicated VMs)
`--external-cloud-provider`	`true`	Install the DigitalOcean CCM and CSI (cloud-provider=external) for LoadBalancers and persistent volumes (default on; pass —external-cloud-provider=false to skip, which also disables —include-networking)
`--gitops-branch`	`master`	GitOps branch to commit to
`--gitops-credential-name`		GitOps GitHub credential name; when set with —gitops-repository, the generated digitalocean-cloud-provider stack is committed to Git (optional)
`--gitops-repository`		GitOps repository (e.g. org/repo) to commit the generated stack to (optional)
`--include-networking`	`true`	Install Traefik + cert-manager for ingress (default on; pass —include-networking=false to skip). Requires —external-cloud-provider (the ingress LoadBalancer is provisioned by the cloud controller manager)
`--kubernetes-version`		Kubernetes version (optional; see `ankra cluster k3s-versions` or `ankra cluster kubeadm-versions`)
`--name`		Cluster name (required)
`--network-ip-range`	`10.0.0.0/16`	Network IP range
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--region`		DigitalOcean region (required)
`--ssh-key-credential-id`		SSH key credential ID (required)
`--worker-count`	`1`	Number of worker nodes
`--worker-size`	`s-2vcpu-4gb`	Worker droplet size

ankra cluster digitalocean k8s-version

Get current Kubernetes version for an DigitalOcean cluster

ankra cluster digitalocean k8s-version <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster digitalocean node-group

List, add, scale, upgrade, and delete node groups.

ankra cluster digitalocean nodes

Inspect every server Ankra manages for the cluster (control plane, workers, and bastion or gateway). Soft-deleted entries from a stopped cluster are included so the saved topology is visible before re-provisioning.

ankra cluster digitalocean nodes get

Show full spec and metadata for a single node

ankra cluster digitalocean nodes get <cluster_id> <node_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster digitalocean nodes list

List all nodes for the cluster

ankra cluster digitalocean nodes list <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster digitalocean nodes restart

Schedule a native reboot (falling back to a power cycle) of the node as a tracked operation. The node must be in the ‘up’ state and have no restart already in flight. Workloads on the node are briefly unavailable while it reboots. Works for any node returned by ‘nodes list’, including the bastion/gateway.

ankra cluster digitalocean nodes restart <cluster_id> <node_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster digitalocean regions

List the DigitalOcean regions the supplied credential can deploy in.

ankra cluster digitalocean regions [flags]

Flags

Flag	Default	Description
`--credential-id`		DigitalOcean API credential ID (required)

ankra cluster digitalocean sizes

List DigitalOcean droplet sizes. Pass —region to filter by region availability.

ankra cluster digitalocean sizes [flags]

Flags

Flag	Default	Description
`--available-only`	`false`	Show only sizes available in the selected region
`--credential-id`		DigitalOcean API credential ID (required)
`--region`		Filter by region slug

ankra cluster digitalocean start

Start (re-provision) a stopped DigitalOcean cluster. Use —scope control_plane to bring up only the control plane.

ankra cluster digitalocean start <cluster_id> [flags]

Flags

Flag	Default	Description
`--scope`	`all`	Provisioning scope: ‘all’ or ‘control_plane’

ankra cluster digitalocean stop

Stop an DigitalOcean cluster’s compute while keeping its configuration so it can be started again later.

ankra cluster digitalocean stop <cluster_id> [flags]

Flags

Flag	Default	Description
`--force`	`false`	Also delete the cluster’s block storage volumes and load balancers (destroys persisted data; they otherwise keep billing while stopped)

ankra cluster digitalocean workers

Get current worker count for an DigitalOcean cluster

ankra cluster digitalocean workers <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster domain

Show the cluster’s generated public domain, queueing the zone if the cluster does not have one yet. The domain nests under the organisation’s Ankra-managed root (ankra.cc by default; organisations may select another offered root, such as smartoptics.dev, in the organisation’s AI environment settings). The call is idempotent: a cluster that already has a zone reports its existing domain unchanged, so this doubles as a lookup. A fresh zone reads “pending” until it is published to the authoritative nameservers and then turns “active”; external-dns is wired to it on the next cloud-provider pass, after which any ingress hostname under the domain resolves with TLS. —remove hands the zone back for teardown instead: the removal step before an organisation switches its Ankra root domain (the switch is refused while cluster zones still live under the old root). A later call without —remove re-enables it under the organisation’s current root.

ankra cluster domain <cluster> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--remove`	`false`	Remove the cluster’s generated public domain (tear the zone down) instead of enabling it

ankra cluster draft

Stage all changes in an ImportCluster YAML as drafts on the cluster without deploying anything. The local checks run first (the same ones as ‘ankra cluster apply —dry-run’), then each stack in the file is saved as a resource draft you can review, edit, and deploy from the Ankra stack builder. If the cluster does not exist yet it is imported first without its stacks, since drafts can only be attached to an existing cluster; every stack in the file is then staged as a draft. Stacks that already match the cluster’s desired state are reported as “no changes” rather than creating an empty draft.

ankra cluster draft [flags]

Flags

Flag	Default	Description
`-f`, `--file`		Path to the ImportCluster YAML file to stage as drafts
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster encrypt

Encrypt sensitive values in manifest or addon configuration files using SOPS.

ankra cluster encrypt addon

Encrypt one or more keys in an addon’s Helm values using SOPS. —key takes the YAML key name whose values should be encrypted. Repeat —key to encrypt several keys in a single run; all keys are encrypted in one SOPS pass and one write. SOPS matches key names anywhere in the document, not dotted paths; a dotted —key is normalised to its last segment. A key whose own name starts with a dot (such as “.dockerconfigjson”) is kept literally. After encrypting, the CLI verifies every value is actually ENC[…] ciphertext and fails if any is not. Two modes: Cluster mode (default): fetch the addon’s values from a live cluster, encrypt the key, and push the result back via the partial-stack PATCH endpoint. The owning stack is resolved automatically. File mode (-f cluster.yaml): rewrite the local addon values file referenced by the cluster.yaml in place, adding the key to encrypted_paths. Examples:

Cluster mode against the selected cluster

ankra cluster encrypt addon —name grafana —key adminPassword

Cluster mode against a specific cluster, disambiguating stack

ankra cluster encrypt addon —name grafana —key adminPassword —cluster prod —stack monitoring

Encrypt several keys in one run

ankra cluster encrypt addon —name grafana —key adminPassword —key smtpPassword

File mode

ankra cluster encrypt addon —name grafana —key adminPassword -f cluster.yaml

ankra cluster encrypt addon [flags]

Flags

Flag	Default	Description
`--cluster`		Target cluster (name or ID); defaults to the active selection (cluster mode)
`-f`, `--file`		Path to a local cluster YAML (enables file mode)
`--key`	`[]`	YAML key name to encrypt (required; repeatable); dotted paths are normalised to the last segment, a leading-dot key like .dockerconfigjson is kept literally
`--name`		Name of the addon (required)
`--stack`		Stack name (cluster mode; required when the addon exists in multiple stacks)

ankra cluster encrypt manifest

Encrypt one or more keys in a manifest using SOPS. —key takes the YAML key name whose values should be encrypted (for a Secret’s data.password, that is “password”). Repeat —key to encrypt several keys in a single run; all keys are encrypted in one SOPS pass and one write. SOPS matches key names anywhere in the document, not dotted paths; a dotted —key is normalised to its last segment. A key whose own name starts with a dot (such as “.dockerconfigjson” in a kubernetes.io/dockerconfigjson Secret) is kept literally. After encrypting, the CLI verifies every value is actually ENC[…] ciphertext and fails if any is not. —all-data selects every key under data and stringData of a Kubernetes Secret manifest instead of naming keys individually; keys whose values are already encrypted are skipped. The manifest must be a Secret. —all-data and —key are mutually exclusive. Two modes: Cluster mode (default): fetch the manifest from a live cluster, encrypt the key, and push the result back via the partial-stack PATCH endpoint. The owning stack is resolved automatically. File mode (-f cluster.yaml): rewrite a local cluster.yaml’s referenced from_file in place, adding the key to encrypted_paths in the file. Used by GitOps workflows where the source of truth is on disk. In cluster mode, —set applies value edits in-memory BEFORE encrypting, so the new secret value and its encryption land in a single commit - the plaintext value never reaches git history. This is the recommended way to set a new secret value: ankra cluster encrypt manifest db-secret —key password
—set ‘data.password=aHVudGVyMg==’ —cluster prod (compared to “manifests upgrade —set” followed by “encrypt manifest”, which commits the plaintext value first). Examples:

Cluster mode against the selected cluster

ankra cluster encrypt manifest db-secret —key password

Cluster mode against a specific cluster

ankra cluster encrypt manifest db-secret —key password —cluster prod

Set a new value and encrypt it atomically (single commit, no plaintext)

ankra cluster encrypt manifest db-secret —key password
—set ‘data.password=bmV3LXNlY3JldA==’ —cluster prod

Encrypt several keys in one run

ankra cluster encrypt manifest db-secret —key password —key api-token

Encrypt every data/stringData key of a Secret manifest

ankra cluster encrypt manifest db-secret —all-data —cluster prod

File mode

ankra cluster encrypt manifest db-secret —key password -f cluster.yaml

ankra cluster encrypt manifest <manifest_name> [flags]

Flags

Flag	Default	Description
`--all-data`	`false`	Encrypt every key under data and stringData of a Secret manifest, skipping values that are already encrypted
`--cluster`		Target cluster (name or ID); defaults to the active selection (cluster mode)
`-f`, `--file`		Path to a local cluster YAML (enables file mode)
`--key`	`[]`	YAML key name to encrypt (repeatable); dotted paths are normalised to the last segment, a leading-dot key like .dockerconfigjson is kept literally
`--set`	`[]`	Apply value edits in-memory before encrypting (same syntax as manifests upgrade —set, e.g. —set ‘data.password=bmV3’); the plaintext value never reaches git (cluster mode only; repeatable)

ankra cluster get

Get Kubernetes resources from the active cluster. Examples: ankra cluster get pods ankra cluster get deployments -n kube-system ankra cluster get nodes ankra cluster get services —all-namespaces

ankra cluster get configmaps

List configmaps in the cluster

ankra cluster get configmaps [name] [flags]

Flags

Flag	Default	Description
`-A`, `--all-namespaces`	`false`	List across all namespaces
`--name`		Filter by resource name
`-n`, `--namespace`		Kubernetes namespace
`-o`, `--output`	`table`	Output format: table, json, yaml
`-l`, `--selector`		Label selector

ankra cluster get cronjobs

List cronjobs in the cluster

ankra cluster get cronjobs [name] [flags]

Flags

Flag	Default	Description
`-A`, `--all-namespaces`	`false`	List across all namespaces
`--name`		Filter by resource name
`-n`, `--namespace`		Kubernetes namespace
`-o`, `--output`	`table`	Output format: table, json, yaml
`-l`, `--selector`		Label selector

ankra cluster get daemonsets

List daemonsets in the cluster

ankra cluster get daemonsets [name] [flags]

Flags

Flag	Default	Description
`-A`, `--all-namespaces`	`false`	List across all namespaces
`--name`		Filter by resource name
`-n`, `--namespace`		Kubernetes namespace
`-o`, `--output`	`table`	Output format: table, json, yaml
`-l`, `--selector`		Label selector

ankra cluster get deployments

List deployments in the cluster

ankra cluster get deployments [name] [flags]

Flags

Flag	Default	Description
`-A`, `--all-namespaces`	`false`	List across all namespaces
`--name`		Filter by resource name
`-n`, `--namespace`		Kubernetes namespace
`-o`, `--output`	`table`	Output format: table, json, yaml
`-l`, `--selector`		Label selector

ankra cluster get events

List events in the cluster

ankra cluster get events [name] [flags]

Flags

Flag	Default	Description
`-A`, `--all-namespaces`	`false`	List across all namespaces
`--name`		Filter by resource name
`-n`, `--namespace`		Kubernetes namespace
`-o`, `--output`	`table`	Output format: table, json, yaml
`-l`, `--selector`		Label selector

ankra cluster get ingresses

List ingresses in the cluster

ankra cluster get ingresses [name] [flags]

Flags

Flag	Default	Description
`-A`, `--all-namespaces`	`false`	List across all namespaces
`--name`		Filter by resource name
`-n`, `--namespace`		Kubernetes namespace
`-o`, `--output`	`table`	Output format: table, json, yaml
`-l`, `--selector`		Label selector

ankra cluster get k8s-jobs

List Kubernetes jobs in the cluster

ankra cluster get k8s-jobs [name] [flags]

Flags

Flag	Default	Description
`-A`, `--all-namespaces`	`false`	List across all namespaces
`--name`		Filter by resource name
`-n`, `--namespace`		Kubernetes namespace
`-o`, `--output`	`table`	Output format: table, json, yaml
`-l`, `--selector`		Label selector

ankra cluster get namespaces

List namespaces in the cluster

ankra cluster get namespaces [name] [flags]

Flags

Flag	Default	Description
`--name`		Filter by resource name
`-o`, `--output`	`table`	Output format: table, json, yaml
`-l`, `--selector`		Label selector

ankra cluster get nodes

List nodes in the cluster

ankra cluster get nodes [name] [flags]

Flags

Flag	Default	Description
`--name`		Filter by resource name
`-o`, `--output`	`table`	Output format: table, json, yaml
`-l`, `--selector`		Label selector

ankra cluster get pods

List pods or get a specific pod’s manifest

ankra cluster get pods [name] [flags]

Flags

Flag	Default	Description
`-A`, `--all-namespaces`	`false`	List across all namespaces
`--name`		Filter by pod name (contains)
`-n`, `--namespace`		Kubernetes namespace
`--node`		Filter by node name
`-o`, `--output`	`table`	Output format: table, json, yaml

ankra cluster get resources

Fetch any Kubernetes resource type. Use for kinds not covered by dedicated commands. Kinds outside the core API group need —group (and sometimes —api-version). Example: ankra cluster resources PersistentVolumeClaim -n default ankra cluster resources NetworkPolicy —group networking.k8s.io —all-namespaces ankra cluster resources StorageClass —group storage.k8s.io

ankra cluster get resources <kind> [flags]

Flags

Flag	Default	Description
`-A`, `--all-namespaces`	`false`	List across all namespaces
`--api-version`	`v1`	API version (e.g. v1, v1beta1)
`--group`		API group (e.g. apps, networking.k8s.io)
`--name`		Filter by resource name
`-n`, `--namespace`		Kubernetes namespace
`-o`, `--output`	`table`	Output format: table, json, yaml
`-l`, `--selector`		Label selector

ankra cluster get secrets

List secrets in the cluster

ankra cluster get secrets [name] [flags]

Flags

Flag	Default	Description
`-A`, `--all-namespaces`	`false`	List across all namespaces
`--name`		Filter by resource name
`-n`, `--namespace`		Kubernetes namespace
`-o`, `--output`	`table`	Output format: table, json, yaml
`-l`, `--selector`		Label selector

ankra cluster get services

List services in the cluster

ankra cluster get services [name] [flags]

Flags

Flag	Default	Description
`-A`, `--all-namespaces`	`false`	List across all namespaces
`--name`		Filter by resource name
`-n`, `--namespace`		Kubernetes namespace
`-o`, `--output`	`table`	Output format: table, json, yaml
`-l`, `--selector`		Label selector

ankra cluster get statefulsets

List statefulsets in the cluster

ankra cluster get statefulsets [name] [flags]

Flags

Flag	Default	Description
`-A`, `--all-namespaces`	`false`	List across all namespaces
`--name`		Filter by resource name
`-n`, `--namespace`		Kubernetes namespace
`-o`, `--output`	`table`	Output format: table, json, yaml
`-l`, `--selector`		Label selector

ankra cluster get storageclasses

List storage classes in the cluster

ankra cluster get storageclasses [name] [flags]

Flags

Flag	Default	Description
`--name`		Filter by resource name
`-o`, `--output`	`table`	Output format: table, json, yaml
`-l`, `--selector`		Label selector

ankra cluster gitops

Commands for inspecting which GitOps repository a cluster syncs from.

ankra cluster gitops status

Show the GitOps sync status of a cluster: the repository, branch, and credential it syncs from, the last synced commit, and any pending commit or sync error. If no cluster name is provided, uses the currently selected cluster.

ankra cluster gitops status [cluster_name] [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster helm

Commands to list and uninstall Helm releases running in the cluster.

ankra cluster helm releases

List Helm releases in the cluster

ankra cluster helm releases [flags]

Flags

Flag	Default	Description
`-A`, `--all-namespaces`	`false`	List across all namespaces (default)
`-n`, `--namespace`		Kubernetes namespace
`-o`, `--output`	`table`	Output format: table, json

ankra cluster helm uninstall

Uninstall a Helm release from the cluster

ankra cluster helm uninstall <release_name> [flags]

Flags

Flag	Default	Description
`-n`, `--namespace`		Kubernetes namespace (required)
`--yes`	`false`	Skip the confirmation prompt

ankra cluster hetzner

Commands to create, deprovision, and scale Hetzner clusters.

ankra cluster hetzner bastion

Resize the cluster’s single bastion/gateway node. Find its node ID with ‘nodes list’.

ankra cluster hetzner bastion resize

Resize the bastion/gateway node. The provider’s bastion/gateway update job powers it off, resizes it, and powers it back on, causing brief SSH/NAT downtime for the cluster.

ankra cluster hetzner bastion resize <cluster_id> <instance_type> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--timeout`	`10m0s`	Maximum time to wait when —wait is set
`--wait`	`false`	Wait for the operation to finish and report success or failure (default: submit and return immediately)

ankra cluster hetzner control-plane

ankra cluster hetzner control-plane get

Show the current control plane configuration

ankra cluster hetzner control-plane get <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster hetzner control-plane set-count

Change the controller count (1 or 3)

ankra cluster hetzner control-plane set-count <cluster_id> <count> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster hetzner control-plane set-instance-type

Change the controller instance type

ankra cluster hetzner control-plane set-instance-type <cluster_id> <instance_type> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster hetzner create

Create a new Hetzner cluster

ankra cluster hetzner create [flags]

Flags

Flag	Default	Description
`--bastion-server-type`	`cx23`	Bastion server type
`--control-plane-count`	`1`	Number of control plane nodes
`--control-plane-server-type`	`cx33`	Control plane server type
`--credential-id`		Hetzner API credential ID (required)
`--distribution`	`k3s`	Kubernetes distribution: k3s or kubeadm
`--etcd-node-count`	`3`	Number of dedicated etcd nodes when —etcd-topology=external (3 or 5)
`--etcd-server-type`	`cx33`	Server type for dedicated etcd nodes when —etcd-topology=external
`--etcd-topology`	`stacked`	etcd topology for kubeadm clusters: stacked (on control planes) or external (dedicated VMs)
`--external-cloud-provider`	`true`	Install the Hetzner CCM and CSI (cloud-provider=external) for LoadBalancers and persistent volumes (default on; pass —external-cloud-provider=false to skip, which also disables —include-networking)
`--gitops-branch`	`master`	GitOps branch to commit to
`--gitops-credential-name`		GitOps GitHub credential name; when set with —gitops-repository, the generated hcloud stack is committed to Git (optional)
`--gitops-repository`		GitOps repository (e.g. org/repo) to commit the generated stack to (optional)
`--include-networking`	`true`	Install Traefik + cert-manager for ingress (default on; pass —include-networking=false to skip). Requires —external-cloud-provider (the ingress LoadBalancer is provisioned by the cloud controller manager)
`--kubernetes-version`		Kubernetes version (optional; see `ankra cluster k3s-versions` or `ankra cluster kubeadm-versions`)
`--location`		Hetzner location (required)
`--name`		Cluster name (required)
`--network-ip-range`	`10.0.0.0/16`	Network IP range
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--ssh-key-credential-id`		SSH key credential ID (single key, use —ssh-key-credential-ids for multiple)
`--ssh-key-credential-ids`	`[]`	SSH key credential IDs (comma-separated or repeated)
`--subnet-range`	`10.0.1.0/24`	Subnet range
`--worker-count`	`1`	Number of worker nodes
`--worker-server-type`	`cx33`	Worker server type

ankra cluster hetzner k8s-version

Get current Kubernetes version for a Hetzner cluster

ankra cluster hetzner k8s-version <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster hetzner locations

List the Hetzner Cloud locations the supplied credential can deploy in. Only these locations are valid for cluster creation.

ankra cluster hetzner locations [flags]

Flags

Flag	Default	Description
`--credential-id`		Hetzner API credential ID (required)

ankra cluster hetzner node-group

List, add, scale, upgrade, and delete node groups.

ankra cluster hetzner nodes

ankra cluster hetzner nodes get

Show full spec and metadata for a single node

ankra cluster hetzner nodes get <cluster_id> <node_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster hetzner nodes list

List all nodes for the cluster

ankra cluster hetzner nodes list <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster hetzner nodes restart

ankra cluster hetzner nodes restart <cluster_id> <node_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster hetzner server-types

List Hetzner Cloud server types. Pass —location to see which types are currently available for provisioning there, and —available-only to hide the rest.

ankra cluster hetzner server-types [flags]

Flags

Flag	Default	Description
`--available-only`	`false`	Only show server types available for provisioning (use with —location)
`--credential-id`		Hetzner API credential ID (required)
`--location`		Filter availability by location

ankra cluster hetzner start

Start (re-provision) a stopped Hetzner cluster. Use —scope control_plane to bring up only the control plane.

ankra cluster hetzner start <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--scope`	`all`	Provisioning scope: ‘all’ or ‘control_plane’

ankra cluster hetzner stop

Stop a Hetzner cluster’s compute while keeping its configuration so it can be started again later.

ankra cluster hetzner stop <cluster_id> [flags]

Flags

Flag	Default	Description
`--force`	`false`	Also delete the cluster’s CSI volumes and load balancers (destroys persisted data; they otherwise keep billing while stopped)
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster hetzner workers

Get current worker count for a Hetzner cluster

ankra cluster hetzner workers <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster info

Show details of a specific cluster. If no name is provided, shows details for the currently selected cluster.

ankra cluster info [name] [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster k3s-versions

List the k3s versions the platform can provision or upgrade to. Use one of these values with ankra cluster upgrade <cluster_id> <target_version> (the provider is detected automatically).

ankra cluster k3s-versions

ankra cluster kube-token

Print a short-lived Kubernetes ExecCredential so kubectl can authenticate to the Ankra cluster gateway. This command is intended to be invoked by kubectl as a client-go credential plugin, for example in a kubeconfig: users:

name: ankra user: exec: apiVersion: client.authentication.k8s.io/v1 command: ankra args: [“cluster”, “kube-token”, “—cluster”, “<cluster-name-or-id>”, “—org”, “<organisation-id>”]

Pinning —org to the cluster’s organisation ID keeps the entry working when your selected organisation differs from the cluster’s (‘ankra cluster kubeconfig add’ writes it automatically). It prints JSON to stdout and never prompts; run ‘ankra login’ first.

ankra cluster kube-token [flags]

Flags

Flag	Default	Description
`--cluster`		Cluster name or ID (defaults to the selected cluster)

ankra cluster kubeadm-versions

List the upstream Kubernetes versions the platform can provision or upgrade kubeadm-distribution clusters to. Use one of these values with --kubernetes-version on ankra cluster <provider> create --distribution kubeadm, or with ankra cluster upgrade <cluster_id> <target_version>.

ankra cluster kubeadm-versions

ankra cluster kubeconfig

Add, remove, and list the Ankra cluster contexts in your kubeconfig. By default ‘add’ writes an exec-based context that fetches a short-lived token on demand via ‘ankra cluster kube-token’, so credentials stay ephemeral and SSO-backed (run ‘ankra login’ once). Other clusters/users/contexts already in your kubeconfig are left untouched. These commands read and write a single file: —kubeconfig if given, otherwise the first entry of $KUBECONFIG, otherwise ~/.kube/config. Examples: ankra cluster kubeconfig add my-cluster —use ankra cluster kubeconfig add —all ankra cluster kubeconfig add my-cluster —print > my-cluster.yaml ankra cluster kubeconfig list ankra cluster kubeconfig remove my-cluster ankra cluster kubeconfig remove —all

ankra cluster kubeconfig add

Add or update an Ankra context in your kubeconfig

ankra cluster kubeconfig add [cluster] [flags]

Flags

Flag	Default	Description
`--all`	`false`	Add every cluster you can access
`--cluster`		Cluster name or ID (same as the positional argument; defaults to the selected cluster)
`--embed-token`	`false`	Embed a short-lived token instead of the exec credential plugin
`--exec-command`	`ankra`	Executable kubectl invokes for credentials in exec mode (use an absolute path if ‘ankra’ is not on PATH)
`--insecure-skip-tls-verify`	`false`	Skip TLS verification for the cluster server (dev only)
`--kubeconfig`		Path to the kubeconfig file (default: $KUBECONFIG or ~/.kube/config)
`--namespace`		Default namespace for the context
`--print`	`false`	Print a standalone kubeconfig to stdout instead of writing the file
`--use`	`false`	Set the added context as the active current-context

ankra cluster kubeconfig list

List Ankra-managed contexts in your kubeconfig

ankra cluster kubeconfig list [flags]

Flags

Flag	Default	Description
`--kubeconfig`		Path to the kubeconfig file (default: $KUBECONFIG or ~/.kube/config)

ankra cluster kubeconfig remove

Remove Ankra contexts from your kubeconfig

ankra cluster kubeconfig remove [cluster] [flags]

Flags

Flag	Default	Description
`--all`	`false`	Remove all Ankra-managed contexts
`--cluster`		Cluster name or ID (same as the positional argument)
`--kubeconfig`		Path to the kubeconfig file (default: $KUBECONFIG or ~/.kube/config)

ankra cluster list

List all clusters

ankra cluster list [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster logs

Stream log output from a pod in the active cluster. By default the stream stays open and prints new lines as they arrive, like kubectl logs -f. Pass —follow=false to print the current backlog and exit, which is what a pipeline into grep or a script wants. Example: ankra cluster logs my-pod -n default -c my-container —tail 100 ankra cluster logs my-pod -n default —since 600 —follow=false | grep ERROR

ankra cluster logs <pod_name> [flags]

Flags

Flag	Default	Description
`-c`, `--container`		Container name (defaults to pod name)
`-f`, `--follow`	`true`	Keep the stream open for new lines; —follow=false prints the current backlog and exits
`-n`, `--namespace`		Kubernetes namespace (required)
`--since`	`0`	Seconds of logs to retrieve
`--tail`	`0`	Number of lines from the end of the logs

ankra cluster managed

Create, delete, stop and start, scale node pools, and upgrade cloud-managed Kubernetes clusters on DOKS, UpCloud UKS, GKE, OVH MKS, AKS, EKS, and Scaleway Kapsule.

ankra cluster managed create

Create a managed Kubernetes cluster

ankra cluster managed create [flags]

Flags

Flag	Default	Description
`--autoscaling`	`false`	Enable autoscaling for the initial node pool
`--autoscaling-max`	`0`	Maximum node count while autoscaling (requires —autoscaling)
`--autoscaling-min`	`0`	Minimum node count while autoscaling (requires —autoscaling)
`--credential-id`		Cloud credential ID
`--gitops-branch`	`master`	GitOps branch (optional)
`--gitops-credential-name`		GitOps credential name (optional)
`--gitops-repository`		GitOps repository URL (optional)
`--kubernetes-version`		Kubernetes version (optional)
`--location`		Region or zone for the cluster
`--name`		Cluster name
`--node-pool-count`	`2`	Initial node pool node count
`--node-pool-name`	`workers`	Initial node pool name
`--node-pool-size`		Initial node pool size/plan
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--private-network-id`		Scaleway private network ID (required with —provider kapsule)
`--provider`		Managed Kubernetes provider (doks, uks, gke, ovh_mks, aks, eks, kapsule)

ankra cluster managed delete

Delete a managed Kubernetes cluster

ankra cluster managed delete <cluster_id> [flags]

Flags

Flag	Default	Description
`--force`	`false`	Force delete even when cluster is in a non-idle state
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--provider`		Managed Kubernetes provider (doks, uks, gke, ovh_mks, aks, eks, kapsule)
`-y`, `--yes`	`false`	Skip confirmation prompt

ankra cluster managed discover

List the managed Kubernetes clusters that already run in the provider account behind a credential, marking the ones already imported into Ankra.

ankra cluster managed discover [flags]

Flags

Flag	Default	Description
`--credential-id`		Cloud credential ID
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--provider`		Managed Kubernetes provider (doks, uks, gke, ovh_mks, aks, eks, kapsule)

ankra cluster managed import

Adopt a managed Kubernetes cluster that already runs at the provider: Ankra fetches the kubeconfig through the provider API and installs the agent automatically, so there is nothing to run against the cluster.

ankra cluster managed import [flags]

Flags

Flag	Default	Description
`--credential-id`		Cloud credential ID
`--description`		Description for the cluster in Ankra (optional)
`--name`		Name for the cluster in Ankra (defaults to the provider-side name)
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--provider`		Managed Kubernetes provider (doks, uks, gke, ovh_mks, aks, eks, kapsule)
`--provider-cluster-id`		Provider-side cluster ID (from discover)

ankra cluster managed node-pool

Manage managed cluster node pools

ankra cluster managed node-pool add

Add a node pool to a managed cluster

ankra cluster managed node-pool add <cluster_id> [flags]

Flags

Flag	Default	Description
`--autoscaling`	`false`	Enable autoscaling for the node pool
`--autoscaling-max`	`0`	Maximum node count while autoscaling (requires —autoscaling)
`--autoscaling-min`	`0`	Minimum node count while autoscaling (requires —autoscaling)
`--count`	`1`	Node count
`--name`		Node pool name
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--provider`		Managed Kubernetes provider (doks, uks, gke, ovh_mks, aks, eks, kapsule)
`--size`		Node pool size/plan

ankra cluster managed node-pool delete

Delete a managed cluster node pool

ankra cluster managed node-pool delete <cluster_id> <node_pool_name> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--provider`		Managed Kubernetes provider (doks, uks, gke, ovh_mks, aks, eks, kapsule)
`-y`, `--yes`	`false`	Skip confirmation prompt

ankra cluster managed node-pool scale

Scale a managed cluster node pool

ankra cluster managed node-pool scale <cluster_id> <node_pool_name> [flags]

Flags

Flag	Default	Description
`--count`	`0`	Target node count
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--provider`		Managed Kubernetes provider (doks, uks, gke, ovh_mks, aks, eks, kapsule)

ankra cluster managed node-pool update

Update the node count or autoscaling settings of a managed cluster node pool. Pass at least one of —count, —autoscaling, —autoscaling-min, or —autoscaling-max; unspecified settings are left unchanged.

ankra cluster managed node-pool update <cluster_id> <node_pool_name> [flags]

Flags

Flag	Default	Description
`--autoscaling`	`false`	Enable (true) or disable (false) autoscaling
`--autoscaling-max`	`0`	Maximum node count while autoscaling
`--autoscaling-min`	`0`	Minimum node count while autoscaling
`--count`	`0`	Target node count
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--provider`		Managed Kubernetes provider (doks, uks, gke, ovh_mks, aks, eks, kapsule)

ankra cluster managed start

Start a stopped managed Kubernetes cluster. Currently only AKS supports stopping and starting managed clusters.

ankra cluster managed start <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--provider`		Managed Kubernetes provider (doks, uks, gke, ovh_mks, aks, eks, kapsule)

ankra cluster managed stop

Stop a managed Kubernetes cluster’s compute while keeping its configuration so it can be started again later. Currently only AKS supports stopping and starting managed clusters.

ankra cluster managed stop <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--provider`		Managed Kubernetes provider (doks, uks, gke, ovh_mks, aks, eks, kapsule)

ankra cluster managed upgrade

Upgrade a managed cluster Kubernetes version

ankra cluster managed upgrade <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--provider`		Managed Kubernetes provider (doks, uks, gke, ovh_mks, aks, eks, kapsule)
`--version`		Target Kubernetes version
`-y`, `--yes`	`false`	Skip confirmation prompt

ankra cluster manifests

Commands to list, view, upgrade, and delete manifests.

ankra cluster manifests delete

Disconnect a manifest from its stack. The manifest’s resources are removed from the cluster and dependent resources are reconnected to the manifest’s own parents. The owning stack is discovered automatically (manifest names are unique per cluster). Use —dry-run to preview the target without making changes.

ankra cluster manifests delete <manifest_name> [flags]

Flags

Flag	Default	Description
`--cluster`		Target cluster (name or ID); defaults to the active selection
`--dry-run`	`false`	Print the manifest that would be disconnected without making changes
`--yes`	`false`	Skip the confirmation prompt

ankra cluster manifests get

Print the current YAML content of a manifest. By default the decoded YAML is written to stdout, making it easy to pipe into a file or edit and re-apply with —from-file: ankra cluster manifests get web > web.yaml ankra cluster manifests get web -o raw # base64-encoded form

ankra cluster manifests get <manifest_name> [flags]

Flags

Flag	Default	Description
`--cluster`		Target cluster (name or ID); defaults to the active selection
`-o`, `--output`		Output format: yaml (decoded, default) or raw (base64)

ankra cluster manifests list

List manifests for the active cluster; or show details for a single manifest

ankra cluster manifests list [manifest name] [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster manifests upgrade

Upgrade a manifest by patching just the fields you supply. At least one mutating flag is required. Examples:

Patch a single path in-place, e.g. bump a Deployment image tag

ankra cluster manifests upgrade web
—set ‘spec.template.spec.containers[name=app].image=nginx:1.27’
—cluster website-demo

When the manifest holds multiple documents, select which one to edit

ankra cluster manifests upgrade web —target-kind Deployment —target-name web
—set ‘spec.replicas=3’ —cluster website-demo

Replace the manifest content from a file

ankra cluster manifests upgrade demo-namespace
—from-file manifests/demo-namespace.yaml —cluster website-demo

Read the manifest from stdin

cat manifest.yaml | ankra cluster manifests upgrade demo-namespace
—manifest - —cluster website-demo —set/—set-string/—set-file MUTATE the existing manifest YAML and address list items by a stable field (e.g. containers[name=app]) as well as by numeric index (containers[0]). —from-file / —manifest - REPLACE the whole manifest and are mutually exclusive with —set*. —from-file / —manifest - accept SOPS-encrypted content: when the file carries a top-level sops: metadata mapping, the keys holding ENC[…] ciphertext are detected and recorded as encrypted_paths automatically (merged with the manifest’s existing encrypted_paths). Use —encrypted-path to declare keys explicitly when auto-detection cannot see them. When no content or —set flag is supplied, the existing content is re-sent unchanged (only namespace is updated). This is required because the backend’s manifest validation rejects empty manifest_base64.

ankra cluster manifests upgrade <manifest_name> [flags]

Flags

Flag	Default	Description
`--add-parent`	`[]`	Add a dependency parent, e.g. —add-parent name=infisical-ns,kind=manifest (kind defaults to manifest; repeatable)
`--cluster`		Target cluster (name or ID); defaults to the active selection
`--dry-run`	`false`	Print the proposed before/after spec without applying changes
`--encrypted-path`	`[]`	With —from-file / —manifest -: declare a YAML key name that is (or must stay) SOPS-encrypted; merged with auto-detected ENC[…] keys and the manifest’s existing encrypted_paths (repeatable)
`--from-file`		Path to manifest YAML file (REPLACES the entire manifest)
`--manifest`		Use `-` to read manifest YAML from stdin (REPLACES the entire manifest)
`--namespace`		Change the manifest’s namespace
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--remove-parent`	`[]`	Remove a dependency parent, e.g. —remove-parent name=infisical-ns,kind=manifest (repeatable)
`--set`	`[]`	In-place edit of the manifest YAML, e.g. —set ‘spec.template.spec.containers[name=app].image=nginx:1.27’ (MUTATES existing content; repeatable, comma-separated)
`--set-file`	`[]`	Like —set but reads the value from a file: key=path or key=@path
`--set-parent`	`[]`	Replace ALL dependency parents with the given set (repeatable)
`--set-string`	`[]`	Like —set but always treats the value as a string
`--target-kind`		With —set: select the document to edit by Kubernetes kind (e.g. Deployment) when the manifest holds multiple documents
`--target-name`		With —set: select the document to edit by metadata.name when the manifest holds multiple documents
`--yes`	`false`	Skip confirmation prompts

ankra cluster metrics

Query the Prometheus metrics source configured for a cluster. The query is proxied through the Ankra agent to the in-cluster Prometheus endpoint configured in Cluster Settings > Metrics. Flags

Flag	Default	Description
`--cluster`		Cluster name (defaults to the selected cluster)

ankra cluster metrics query

Run an instant PromQL query against the cluster’s Prometheus source. Examples: ankra cluster metrics query ‘up’ ankra cluster metrics query ‘sum(rate(container_cpu_usage_seconds_total[5m])) by (pod)’

ankra cluster metrics query [promql] [flags]

Flags

Flag	Default	Description
`-o`, `--output`	`table`	Output format: table, json, yaml
`--timeout`	`0`	Query timeout in seconds (default server-side)

ankra cluster metrics query-range

Run a range PromQL query against the cluster’s Prometheus source. Provide either —range (a duration relative to now) or both —start and —end (Unix seconds). When —step is omitted a sensible step is chosen automatically. Examples: ankra cluster metrics query-range ‘up’ —range 1h ankra cluster metrics query-range ‘rate(node_cpu_seconds_total[5m])’ —range 6h —step 5m ankra cluster metrics query-range ‘up’ —start 1717000000 —end 1717003600 —step 1m

ankra cluster metrics query-range [promql] [flags]

Flags

Flag	Default	Description
`--end`		Range end as Unix seconds (use with —start)
`-o`, `--output`	`table`	Output format: table, json, yaml
`--range`		Duration relative to now (e.g. 15m, 1h, 6h, 24h, 7d)
`--start`		Range start as Unix seconds (use with —end)
`--step`		Resolution step (e.g. 30s, 1m, 5m)
`--timeout`	`0`	Query timeout in seconds (default server-side)

ankra cluster morpheus

Commands to create, stop, start, and inspect HPE Morpheus clusters.

ankra cluster morpheus clouds

List HPE Morpheus clouds available to a credential

ankra cluster morpheus clouds [flags]

Flags

Flag	Default	Description
`--credential-id`		HPE Morpheus API credential ID (required)

ankra cluster morpheus control-plane

ankra cluster morpheus control-plane get

Show the current control plane configuration

ankra cluster morpheus control-plane get <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster morpheus control-plane set-count

Change the controller count (1 or 3)

ankra cluster morpheus control-plane set-count <cluster_id> <count> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster morpheus control-plane set-instance-type

Change the controller instance type

ankra cluster morpheus control-plane set-instance-type <cluster_id> <instance_type> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster morpheus create

Create a new HPE Morpheus cluster

ankra cluster morpheus create [flags]

Flags

Flag	Default	Description
`--bastion-plan-id`	`0`	Service plan ID for the bastion (required; see `ankra cluster morpheus plans`)
`--cloud-id`	`0`	Morpheus cloud ID (required; see `ankra cluster morpheus clouds`)
`--cni`		CNI plugin (optional; the platform default is used when omitted)
`--control-plane-count`	`1`	Number of control plane nodes
`--control-plane-plan-id`	`0`	Service plan ID for control plane nodes (required)
`--credential-id`		HPE Morpheus API credential ID (required)
`--description`		Cluster description
`--distribution`	`k3s`	Kubernetes distribution: k3s or kubeadm
`--etcd-node-count`	`3`	Number of dedicated etcd nodes when —etcd-topology=external (3 or 5)
`--etcd-plan-id`	`0`	Service plan ID for dedicated etcd nodes when —etcd-topology=external (optional)
`--etcd-topology`	`stacked`	etcd topology for kubeadm clusters: stacked (on control plane) or external (dedicated instances)
`--group-id`	`0`	Morpheus group ID (required; see `ankra cluster morpheus groups`)
`--include-networking`	`true`	Install Traefik + cert-manager as Ankra-managed stacks for ingress (exposed via the built-in k3s service load balancer; default on)
`--kubernetes-version`		Kubernetes version (optional; see `ankra cluster k3s-versions` or `ankra cluster kubeadm-versions`)
`--layout-id`	`0`	Morpheus instance-type layout ID (required; see `ankra cluster morpheus layouts`)
`--name`		Cluster name (required)
`--network-id`	`0`	Morpheus network ID (required; see `ankra cluster morpheus networks`)
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--ssh-key-credential-id`		SSH key credential ID (required)
`--virtual-image-id`	`0`	Morpheus virtual image ID (optional)
`--worker-count`	`1`	Number of worker nodes
`--worker-plan-id`	`0`	Service plan ID for worker nodes (required)

ankra cluster morpheus groups

List HPE Morpheus groups available to a credential

ankra cluster morpheus groups [flags]

Flags

Flag	Default	Description
`--credential-id`		HPE Morpheus API credential ID (required)

ankra cluster morpheus k8s-version

Get current Kubernetes version for an HPE Morpheus cluster

ankra cluster morpheus k8s-version <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster morpheus layouts

List HPE Morpheus instance-type layouts available to a credential

ankra cluster morpheus layouts [flags]

Flags

Flag	Default	Description
`--credential-id`		HPE Morpheus API credential ID (required)

ankra cluster morpheus networks

List HPE Morpheus networks available to a credential

ankra cluster morpheus networks [flags]

Flags

Flag	Default	Description
`--credential-id`		HPE Morpheus API credential ID (required)

ankra cluster morpheus nodes

ankra cluster morpheus nodes get

Show full spec and metadata for a single node

ankra cluster morpheus nodes get <cluster_id> <node_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster morpheus nodes list

List all nodes for the cluster

ankra cluster morpheus nodes list <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster morpheus plans

List HPE Morpheus service plans available to a credential

ankra cluster morpheus plans [flags]

Flags

Flag	Default	Description
`--credential-id`		HPE Morpheus API credential ID (required)

ankra cluster morpheus start

Start (re-provision) a stopped HPE Morpheus cluster. Use —scope control_plane to bring up only the control plane.

ankra cluster morpheus start <cluster_id> [flags]

Flags

Flag	Default	Description
`--scope`	`all`	Provisioning scope: ‘all’ or ‘control_plane’

ankra cluster morpheus stop

Stop an HPE Morpheus cluster’s instances while keeping its configuration so it can be started again later.

ankra cluster morpheus stop <cluster_id>

ankra cluster morpheus workers

Get current worker count for an HPE Morpheus cluster

ankra cluster morpheus workers <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster node-group

List, add, scale, upgrade, and delete node groups on a cloud cluster. The cloud provider (Hetzner, OVH, UpCloud, DigitalOcean, Proxmox VE, or HPE Morpheus) is detected automatically from the cluster.

ankra cluster node-group add

Add a node group

ankra cluster node-group add <cluster_id> [flags]

Flags

Flag	Default	Description
`--availability-zone`		Pin every node of the group to one availability zone, on OVH 3-AZ regions (e.g. eu-west-par-b). See ‘ankra cluster ovh regions —with-zones’. Pin the group when it runs zonal storage: an OVH volume cannot attach from another zone
`--count`	`1`	Number of nodes
`--instance-type`		Server type / flavor / plan for nodes (required)
`--name`		Node group name (required)
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--timeout`	`10m0s`	Maximum time to wait when —wait is set
`--wait`	`false`	Wait for the operation to finish and report success or failure (default: submit and return immediately)

ankra cluster node-group autoscaling

Read or write the Cluster Autoscaler settings of a node group. When autoscaling is enabled, the Ankra-managed Cluster Autoscaler keeps the group’s node count within [min, max] based on pod demand. Manual scaling stays allowed but is clamped into the same bounds.

ankra cluster node-group autoscaling get

Show autoscaling settings for a node group

ankra cluster node-group autoscaling get <cluster_id> <group_name> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster node-group autoscaling set

Enable autoscaling with —enabled —min <n> —max <n>, or disable it with —enabled=false. min must be at least 1 (scale-to-zero is not supported); enabling requires the cluster’s ankra-agent to be recent enough to serve the autoscaler, and installs the Cluster Autoscaler on first enable.

ankra cluster node-group autoscaling set <cluster_id> <group_name> [flags]

Flags

Flag	Default	Description
`--enabled`	`true`	Enable (true) or disable (false) autoscaling
`--max`	`5`	Maximum node count while autoscaling
`--min`	`1`	Minimum node count while autoscaling (>= 1)
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--timeout`	`10m0s`	Maximum time to wait when —wait is set
`--wait`	`false`	Wait for the operation to finish and report success or failure (default: submit and return immediately)

ankra cluster node-group delete

Delete a node group and all its nodes

ankra cluster node-group delete <cluster_id> <group_name> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--timeout`	`10m0s`	Maximum time to wait when —wait is set
`--wait`	`false`	Wait for the operation to finish and report success or failure (default: submit and return immediately)
`--yes`	`false`	Skip the confirmation prompt

ankra cluster node-group labels

Replace the labels on every node in the group. Pass —labels as a comma-separated list of key=value pairs, or —clear to remove all labels. The cloud provider is detected automatically from the cluster.

ankra cluster node-group labels <cluster_id> <group_name> [flags]

Flags

Flag	Default	Description
`--clear`	`false`	Remove all labels from the node group
`--labels`		Comma-separated key=value pairs to set on the group
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--timeout`	`10m0s`	Maximum time to wait when —wait is set
`--wait`	`false`	Wait for the operation to finish and report success or failure (default: submit and return immediately)

ankra cluster node-group list

List node groups

ankra cluster node-group list <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster node-group scale

Scale a node group

ankra cluster node-group scale <cluster_id> <group_name> <count> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--timeout`	`10m0s`	Maximum time to wait when —wait is set
`--wait`	`false`	Wait for the operation to finish and report success or failure (default: submit and return immediately)

ankra cluster node-group taints

Replace the taints on every node in the group. Pass —taints as a comma-separated list of key=value:Effect (value optional, effect defaults to NoSchedule), or —clear to remove all taints. The cloud provider is detected automatically from the cluster.

ankra cluster node-group taints <cluster_id> <group_name> [flags]

Flags

Flag	Default	Description
`--clear`	`false`	Remove all taints from the node group
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--taints`		Comma-separated key=value:Effect taints to set on the group
`--timeout`	`10m0s`	Maximum time to wait when —wait is set
`--wait`	`false`	Wait for the operation to finish and report success or failure (default: submit and return immediately)

ankra cluster node-group upgrade

Upgrade instance type for a node group (cannot be reversed)

ankra cluster node-group upgrade <cluster_id> <group_name> <instance_type> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--timeout`	`10m0s`	Maximum time to wait when —wait is set
`--wait`	`false`	Wait for the operation to finish and report success or failure (default: submit and return immediately)

ankra cluster operations

Commands to list, inspect, retry, and cancel executions and their steps.

ankra cluster operations cancel

Cancel one or more running executions

ankra cluster operations cancel <execution_id> [<execution_id>...] [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster operations cancel-step

Cancel a specific step within an execution

ankra cluster operations cancel-step <execution_id> <step_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster operations list

List executions for the active cluster; optionally, provide an ID for details

ankra cluster operations list [execution ID] [flags]

Flags

Flag	Default	Description
`--failed`	`false`	Shortcut for —status failed —status critical
`--interval`	`5s`	Polling interval used when —watch is set
`--limit`	`50`	Maximum number of executions to return (max 100)
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--status`	`[]`	Filter by execution status (repeatable). Examples: failed, critical, running
`-w`, `--watch`	`false`	Continuously poll and refresh until all executions reach a terminal state

ankra cluster operations retry

Retry a terminal execution (failed/cancelled/timeout)

ankra cluster operations retry <execution_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster operations steps

List the steps of an execution with their status and error excerpt. —results additionally fetches each step’s job result - the structured payload the scheduler recorded when the step finished (for example the resources a teardown deleted, skipped, or failed to reclaim). Results are printed under each step, and merged into the steps in -o json|yaml output.

ankra cluster operations steps <execution_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--results`	`false`	Also fetch and show each step’s recorded job result (what the step created, deleted, skipped, or failed to reclaim)

ankra cluster ovh

Commands to create, deprovision, and scale OVH Cloud clusters.

ankra cluster ovh access-info

Show the gateway (bastion) and control plane IPs plus ready-to-use SSH jump and Kubernetes API port-forward commands.

ankra cluster ovh access-info <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster ovh bastion

Resize the cluster’s single bastion/gateway node. Find its node ID with ‘nodes list’.

ankra cluster ovh bastion resize

Resize the bastion/gateway node. The provider’s bastion/gateway update job powers it off, resizes it, and powers it back on, causing brief SSH/NAT downtime for the cluster.

ankra cluster ovh bastion resize <cluster_id> <instance_type> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--timeout`	`10m0s`	Maximum time to wait when —wait is set
`--wait`	`false`	Wait for the operation to finish and report success or failure (default: submit and return immediately)

ankra cluster ovh control-plane

ankra cluster ovh control-plane get

Show the current control plane configuration

ankra cluster ovh control-plane get <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster ovh control-plane set-count

Change the controller count (1 or 3)

ankra cluster ovh control-plane set-count <cluster_id> <count> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster ovh control-plane set-instance-type

Change the controller instance type

ankra cluster ovh control-plane set-instance-type <cluster_id> <instance_type> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster ovh create

Create a new OVH cluster

ankra cluster ovh create [flags]

Flags

Flag	Default	Description
`--availability-zones`	`[]`	Availability zones to spread the cluster across, in a 3-AZ region (e.g. eu-west-par-a,eu-west-par-b,eu-west-par-c). See ‘ankra cluster ovh regions —with-zones’. Omitted leaves placement to OVH, which puts every node in one zone. More than one zone needs —control-plane-count=3 for etcd quorum
`--control-plane-count`	`1`	Number of control plane nodes
`--control-plane-flavor-id`	`b2-15`	Control plane instance flavor
`--credential-id`		OVH API credential ID (required)
`--dhcp-end`	`10.0.1.200`	DHCP range end
`--dhcp-start`	`10.0.1.100`	DHCP range start
`--distribution`	`k3s`	Kubernetes distribution: k3s or kubeadm
`--etcd-flavor-id`	`b2-15`	Instance flavor for dedicated etcd nodes when —etcd-topology=external
`--etcd-node-count`	`3`	Number of dedicated etcd nodes when —etcd-topology=external (3 or 5)
`--etcd-topology`	`stacked`	etcd topology for kubeadm clusters: stacked (on control planes) or external (dedicated VMs)
`--external-cloud-provider`	`true`	Install the OpenStack CCM and Cinder CSI (cloud-provider=external) for LoadBalancers and persistent volumes (default on; pass —external-cloud-provider=false to skip, which also disables —include-networking)
`--gateway-flavor-id`	`b2-7`	Gateway instance flavor
`--gitops-branch`	`master`	GitOps branch to commit to
`--gitops-credential-name`		GitOps GitHub credential name; when set with —gitops-repository, the generated ovh-cloud stack is committed to Git (optional)
`--gitops-repository`		GitOps repository (e.g. org/repo) to commit the generated stack to (optional)
`--include-networking`	`true`	Install Traefik + cert-manager for ingress (default on; pass —include-networking=false to skip). Requires —external-cloud-provider (the ingress LoadBalancer is provisioned by the cloud controller manager)
`--kubernetes-version`		Kubernetes version (optional; see `ankra cluster k3s-versions` or `ankra cluster kubeadm-versions`)
`--name`		Cluster name (required)
`--network-vlan-id`	`0`	Network VLAN ID
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--region`		OVH Cloud region (required)
`--ssh-key-credential-id`		SSH key credential ID (required)
`--subnet-cidr`	`10.0.1.0/24`	Subnet CIDR
`--worker-count`	`1`	Number of worker nodes
`--worker-flavor-id`	`b2-15`	Worker instance flavor

ankra cluster ovh k8s-version

Get current Kubernetes version for an OVH cluster

ankra cluster ovh k8s-version <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster ovh node-group

List, add, scale, upgrade, label, taint, and delete node groups.

ankra cluster ovh nodes

ankra cluster ovh nodes get

Show full spec and metadata for a single node

ankra cluster ovh nodes get <cluster_id> <node_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster ovh nodes list

List all nodes for the cluster

ankra cluster ovh nodes list <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster ovh nodes restart

ankra cluster ovh nodes restart <cluster_id> <node_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster ovh regions

List the OVH Cloud regions the supplied credential’s project can deploy in. Only these regions are valid for cluster creation.

ankra cluster ovh regions [flags]

Flags

Flag	Default	Description
`--credential-id`		OVH API credential ID (required)
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--with-zones`	`false`	Also show each region’s type and availability zones. Only region-3-az regions can place instances by zone; the zone names listed here are what —availability-zones and —availability-zone accept

ankra cluster ovh ssh-keys

Get and set the SSH key credentials authorised to access an OVH cluster’s nodes.

ankra cluster ovh start

Start (re-provision) a stopped OVH cluster. Use —scope control_plane to bring up only the control plane.

ankra cluster ovh start <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--scope`	`all`	Provisioning scope: ‘all’ or ‘control_plane’

ankra cluster ovh stop

Stop an OVH cluster’s compute while keeping its configuration so it can be started again later.

ankra cluster ovh stop <cluster_id> [flags]

Flags

Flag	Default	Description
`--force`	`false`	Also delete the cluster’s Cinder volumes and load balancers (destroys persisted data; they otherwise keep billing while stopped)
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster ovh workers

Get current worker count for an OVH cluster

ankra cluster ovh workers <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster playground

The playground is a real, writable Kubernetes environment Ankra provisions for you - a virtual cluster on Ankra’s own infrastructure, with the agent already installed. Every organisation may hold one; it expires after a period of inactivity.

ankra cluster playground create

Create the organisation’s playground. Provisioning runs in the background: poll ankra cluster playground status <cluster_id> until the phase reaches ready.

ankra cluster playground create

ankra cluster playground status

Show the provisioning phase of a playground

ankra cluster playground status <cluster_id>

ankra cluster power-schedules

Manage the cluster’s power schedules: scheduled stop or start actions that fire once at a chosen time or repeatedly on a cron expression, so a development cluster can park itself outside working hours. Power schedules are available for self-managed Hetzner, OVHcloud, UpCloud, DigitalOcean, Scaleway, Proxmox VE, and HPE Morpheus clusters - the same clusters that support manual stop and start. A scheduled stop behaves exactly like stopping the cluster yourself: the provider VMs are terminated and only the cluster’s configuration is preserved for the next start. Examples:

Park a development cluster on weekday evenings, back before morning

ankra cluster power-schedules create —action stop —cron ‘0 19 * * 1-5’ —timezone Europe/Stockholm ankra cluster power-schedules create —action start —cron ‘0 7 * * 1-5’ —timezone Europe/Stockholm

One-off stop before the weekend

ankra cluster power-schedules create —action stop —at 2026-01-02T19:00:00Z

ankra cluster power-schedules create

Create a scheduled stop or start on the active cluster. The schedule fires once at —at, or repeatedly per —cron evaluated in —timezone (UTC when omitted). A cluster can hold up to 20 schedules.

ankra cluster power-schedules create [flags]

Flags

Flag	Default	Description
`--action`		What the schedule does when it fires: stop or start (required)
`--at`		Fire once at this RFC 3339 time, e.g. 2026-01-02T19:00:00Z (mutually exclusive with —cron)
`--cron`		Fire repeatedly per this 5-field cron expression, e.g. ‘0 19 * * 1-5’ (mutually exclusive with —at)
`--enabled`	`true`	Whether the schedule is armed; —enabled=false creates or leaves it paused
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--timezone`		IANA timezone the cron expression is evaluated in, e.g. Europe/Stockholm (default UTC)

ankra cluster power-schedules delete

Delete a power schedule: it stops firing immediately and disappears from the cluster’s schedule list. The cluster itself is not touched. To pause a schedule while keeping its configuration, use ‘ankra cluster power-schedules update <schedule_id> … —enabled=false’.

ankra cluster power-schedules delete <schedule_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`-y`, `--yes`	`false`	Skip the confirmation prompt

ankra cluster power-schedules list

List the active cluster’s power schedules

ankra cluster power-schedules list [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster power-schedules update

Replace a power schedule. This is a full replace, not a patch: pass the complete schedule as it should be afterwards - —action plus one of —at or —cron (with —timezone for cron schedules), and —enabled=false to leave it paused. Use ‘ankra cluster power-schedules list’ for the schedule ID and the current values.

ankra cluster power-schedules update <schedule_id> [flags]

Flags

Flag	Default	Description
`--action`		What the schedule does when it fires: stop or start (required)
`--at`		Fire once at this RFC 3339 time, e.g. 2026-01-02T19:00:00Z (mutually exclusive with —cron)
`--cron`		Fire repeatedly per this 5-field cron expression, e.g. ‘0 19 * * 1-5’ (mutually exclusive with —at)
`--enabled`	`true`	Whether the schedule is armed; —enabled=false creates or leaves it paused
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--timezone`		IANA timezone the cron expression is evaluated in, e.g. Europe/Stockholm (default UTC)

ankra cluster provision

Start a managed cluster that was previously created but is not yet running. If no cluster name is provided, uses the currently selected cluster.

ankra cluster provision [cluster_name] [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster proxmox

Commands to create, stop, start, and inspect Proxmox VE clusters.

ankra cluster proxmox bridges

List Proxmox VE network bridges on a host node

ankra cluster proxmox bridges [flags]

Flags

Flag	Default	Description
`--credential-id`		Proxmox VE API credential ID (required)
`--node`		Proxmox VE host node (required; see `ankra cluster proxmox hosts`)

ankra cluster proxmox control-plane

ankra cluster proxmox control-plane get

Show the current control plane configuration

ankra cluster proxmox control-plane get <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster proxmox control-plane set-count

Change the controller count (1 or 3)

ankra cluster proxmox control-plane set-count <cluster_id> <count> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster proxmox control-plane set-instance-type

Change the controller instance type

ankra cluster proxmox control-plane set-instance-type <cluster_id> <instance_type> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster proxmox create

Create a new Proxmox VE cluster

ankra cluster proxmox create [flags]

Flags

Flag	Default	Description
`--bastion-instance-type`	`px-small`	Bastion instance-size preset
`--bridge`		Network bridge for cluster VMs (required; see `ankra cluster proxmox bridges`)
`--cni`		CNI plugin (optional; the platform default is used when omitted)
`--control-plane-count`	`1`	Number of control plane nodes
`--control-plane-instance-type`	`px-medium`	Control plane instance-size preset
`--credential-id`		Proxmox VE API credential ID (required)
`--description`		Cluster description
`--distribution`	`k3s`	Kubernetes distribution: k3s or kubeadm
`--etcd-instance-type`	`px-medium`	Instance-size preset for dedicated etcd nodes when —etcd-topology=external
`--etcd-node-count`	`3`	Number of dedicated etcd nodes when —etcd-topology=external (3 or 5)
`--etcd-topology`	`stacked`	etcd topology for kubeadm clusters: stacked (on control plane) or external (dedicated VMs)
`--include-networking`	`true`	Install Traefik + cert-manager as Ankra-managed stacks for ingress (exposed via the built-in k3s service load balancer; default on)
`--kubernetes-version`		Kubernetes version (optional; see `ankra cluster k3s-versions` or `ankra cluster kubeadm-versions`)
`--name`		Cluster name (required)
`--node`		Proxmox VE host node to deploy on (required; see `ankra cluster proxmox hosts`)
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--placement-nodes`	`[]`	Two or more host nodes for host-spread placement (comma-separated or repeated; optional)
`--ssh-key-credential-id`		SSH key credential ID (required)
`--storage`		Storage for VM disks (default local-lvm; see `ankra cluster proxmox storages`)
`--template`		VM template name (optional; the first available template on the node is used when omitted)
`--worker-count`	`1`	Number of worker nodes
`--worker-instance-type`	`px-medium`	Worker instance-size preset

ankra cluster proxmox hosts

List the Proxmox VE host nodes the supplied credential can deploy virtual machines on.

ankra cluster proxmox hosts [flags]

Flags

Flag	Default	Description
`--credential-id`		Proxmox VE API credential ID (required)

ankra cluster proxmox k8s-version

Get current Kubernetes version for a Proxmox VE cluster

ankra cluster proxmox k8s-version <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster proxmox nodes

ankra cluster proxmox nodes get

Show full spec and metadata for a single node

ankra cluster proxmox nodes get <cluster_id> <node_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster proxmox nodes list

List all nodes for the cluster

ankra cluster proxmox nodes list <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster proxmox nodes restart

ankra cluster proxmox nodes restart <cluster_id> <node_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster proxmox sizes

List the instance-size presets (px-small, px-medium, …) accepted by the Proxmox VE instance-type flags.

ankra cluster proxmox sizes

ankra cluster proxmox start

Start (re-provision) a stopped Proxmox VE cluster. Use —scope control_plane to bring up only the control plane.

ankra cluster proxmox start <cluster_id> [flags]

Flags

Flag	Default	Description
`--scope`	`all`	Provisioning scope: ‘all’ or ‘control_plane’

ankra cluster proxmox stop

Stop a Proxmox VE cluster’s virtual machines while keeping its configuration so it can be started again later.

ankra cluster proxmox stop <cluster_id>

ankra cluster proxmox storages

List Proxmox VE storages on a host node

ankra cluster proxmox storages [flags]

Flags

Flag	Default	Description
`--credential-id`		Proxmox VE API credential ID (required)
`--node`		Proxmox VE host node (required; see `ankra cluster proxmox hosts`)

ankra cluster proxmox templates

List Proxmox VE VM templates on a host node

ankra cluster proxmox templates [flags]

Flags

Flag	Default	Description
`--credential-id`		Proxmox VE API credential ID (required)
`--node`		Proxmox VE host node (required; see `ankra cluster proxmox hosts`)

ankra cluster proxmox workers

Get current worker count for a Proxmox VE cluster

ankra cluster proxmox workers <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster reconcile

Trigger a reconciliation for a cluster to sync desired state with actual state. If no cluster name is provided, uses the currently selected cluster. If a cluster name is provided, reconciles that specific cluster.

ankra cluster reconcile [cluster_name] [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster roll-to

Roll a cluster to a specific resource version. Uses the currently selected cluster unless —cluster is provided. Example: ankra cluster roll-to —version abc123

ankra cluster roll-to [flags]

Flags

Flag	Default	Description
`--version`		Resource version ID to roll to (required)

ankra cluster scale

Scale the number of default-pool worker nodes up or down for a cloud cluster. The cloud provider (Hetzner, OVH, UpCloud, DigitalOcean, Proxmox VE, or HPE Morpheus) is detected automatically from the cluster, so you do not need to remember which provider it runs on. To scale a named node group instead, use ‘ankra cluster node-group scale’. Example: ankra cluster scale 62f4559a-a44d-46d7-aab3-a57c9dd6b4c6 3

ankra cluster scale <cluster_id> <worker_count> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster scaleway

Manage the lifecycle of Scaleway clusters.

ankra cluster scaleway nodes

ankra cluster scaleway nodes get

Show full spec and metadata for a single node

ankra cluster scaleway nodes get <cluster_id> <node_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster scaleway nodes list

List all nodes for the cluster

ankra cluster scaleway nodes list <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster scaleway nodes restart

ankra cluster scaleway nodes restart <cluster_id> <node_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster scaleway start

Re-provision a stopped Scaleway cluster. Use —scope control_plane to bring up only the control plane.

ankra cluster scaleway start <cluster_id> [flags]

Flags

Flag	Default	Description
`--scope`	`all`	Provisioning scope: ‘all’ or ‘control_plane’

ankra cluster scaleway stop

Stop a Scaleway cluster by terminating its compute while preserving its configuration so it can be re-provisioned later.

ankra cluster scaleway stop <cluster_id> [flags]

Flags

Flag	Default	Description
`--force`	`false`	Also delete the cluster’s tagged volumes and load balancers even when retention_policy is retain (destroys persisted data)

ankra cluster select

Select a cluster and save it as the active cluster for subsequent commands. If a cluster name is provided, it will be selected directly without prompting. If no name is provided, an interactive picker is shown. Examples: ankra cluster select ankra cluster select my-cluster

ankra cluster select [cluster_name]

ankra cluster sops-config

Show the SOPS encryption configuration including the public key used for encrypting secrets.

ankra cluster sops-config

ankra cluster ssh-keys

Get, set, and re-sync the SSH key credentials authorised to access a cloud cluster’s nodes. The cloud provider (Hetzner, OVH, UpCloud, DigitalOcean, Proxmox VE, or HPE Morpheus) is detected automatically from the cluster.

ankra cluster ssh-keys get

Show SSH keys attached to a cluster

ankra cluster ssh-keys get <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster ssh-keys resync

Re-sync the cluster’s SSH key with the cloud provider. Use this to repair a stale provider-side SSH key reference (for example when the key was deleted and re-created in the provider console) that blocks new node creation, and to re-apply the authorised keys to running nodes.

ankra cluster ssh-keys resync <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster ssh-keys set

Replace the SSH key credentials attached to a cluster. Changes take effect on the next reconciliation and are applied to running nodes. Pass —clear to remove all user SSH keys (the Ankra-managed key always remains).

ankra cluster ssh-keys set <cluster_id> [flags]

Flags

Flag	Default	Description
`--clear`	`false`	Remove all user SSH keys (the Ankra-managed key is retained)
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--ssh-key-credential-ids`	`[]`	SSH key credential IDs (comma-separated or repeated)

ankra cluster stacks

Commands to list, create, delete, rename, and view history of stacks.

ankra cluster stacks clone

Clone a stack from the current cluster to a target cluster. The cloned stack will be created as a draft in the target cluster, allowing you to review and modify it before deployment. Encrypted values will be stripped during cloning for security reasons and will need to be reconfigured in the target cluster.

ankra cluster stacks clone <stack_name> --to <target_cluster> [flags]

Flags

Flag	Default	Description
`--include-config`	`true`	Include addon configurations
`-n`, `--name`		New stack name (optional, defaults to original)
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`-t`, `--to`		Target cluster name or ID (required)

ankra cluster stacks delete

Delete a stack

ankra cluster stacks delete <name> [flags]

Flags

Flag	Default	Description
`--yes`	`false`	Skip the confirmation prompt

ankra cluster stacks history

Show history of changes for a stack

ankra cluster stacks history <name> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster stacks list

List stacks for the active cluster; or show details for a single stack

ankra cluster stacks list [stack name] [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster stacks rename

Rename a stack

ankra cluster stacks rename <old_name> <new_name>

ankra cluster stacks variables

Manage variables on a specific stack. Stack variables are the most specific scope and shadow cluster and organisation variables of the same name when this stack’s manifests/addons are rendered. ankra cluster stacks variables list <stack> ankra cluster stacks variables get <stack> DB_HOST ankra cluster stacks variables set <stack> DB_HOST db.prod.example.com ankra cluster stacks variables delete <stack> DB_HOST Stack variables are stored on the stack spec itself; edits use the same partial-stack PATCH endpoint as manifests/addons upgrade.

ankra cluster stacks variables delete

Delete a variable from a stack

ankra cluster stacks variables delete <stack> <name> [flags]

Flags

Flag	Default	Description
`--cluster`		Target cluster (name or ID); defaults to the active selection
`--yes`	`false`	Skip the confirmation prompt

ankra cluster stacks variables get

Get a single stack variable

ankra cluster stacks variables get <stack> <name> [flags]

Flags

Flag	Default	Description
`--cluster`		Target cluster (name or ID); defaults to the active selection

ankra cluster stacks variables list

List variables on a stack

ankra cluster stacks variables list <stack> [flags]

Flags

Flag	Default	Description
`--cluster`		Target cluster (name or ID); defaults to the active selection
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster stacks variables set

Create or update a stack variable. The value can be read from stdin by passing ”-”.

ankra cluster stacks variables set <stack> <name> <value> [flags]

Flags

Flag	Default	Description
`--cluster`		Target cluster (name or ID); defaults to the active selection
`--dry-run`	`false`	Print the proposed change without writing

ankra cluster upcloud

Commands to create, deprovision, and scale UpCloud clusters.

ankra cluster upcloud bastion

Resize the cluster’s single bastion/gateway node. Find its node ID with ‘nodes list’.

ankra cluster upcloud bastion resize

Resize the bastion/gateway node. The provider’s bastion/gateway update job powers it off, resizes it, and powers it back on, causing brief SSH/NAT downtime for the cluster.

ankra cluster upcloud bastion resize <cluster_id> <instance_type> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--timeout`	`10m0s`	Maximum time to wait when —wait is set
`--wait`	`false`	Wait for the operation to finish and report success or failure (default: submit and return immediately)

ankra cluster upcloud control-plane

ankra cluster upcloud control-plane get

Show the current control plane configuration

ankra cluster upcloud control-plane get <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster upcloud control-plane set-count

Change the controller count (1 or 3)

ankra cluster upcloud control-plane set-count <cluster_id> <count> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster upcloud control-plane set-instance-type

Change the controller instance type

ankra cluster upcloud control-plane set-instance-type <cluster_id> <instance_type> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster upcloud create

Create a new UpCloud cluster

ankra cluster upcloud create [flags]

Flags

Flag	Default	Description
`--bastion-plan`	`1xCPU-2GB`	Bastion plan
`--control-plane-count`	`1`	Number of control plane nodes
`--control-plane-plan`	`2xCPU-4GB`	Control plane plan
`--credential-id`		UpCloud API credential ID (required)
`--distribution`	`k3s`	Kubernetes distribution: k3s or kubeadm
`--etcd-node-count`	`3`	Number of dedicated etcd nodes when —etcd-topology=external (3 or 5)
`--etcd-plan`	`2xCPU-4GB`	Plan for dedicated etcd nodes when —etcd-topology=external
`--etcd-topology`	`stacked`	etcd topology for kubeadm clusters: stacked (on control planes) or external (dedicated VMs)
`--external-cloud-provider`	`true`	Install the UpCloud CCM and CSI (cloud-provider=external) for LoadBalancers and persistent volumes (default on; pass —external-cloud-provider=false to skip, which also disables —include-networking)
`--gitops-branch`	`master`	GitOps branch to commit to
`--gitops-credential-name`		GitOps GitHub credential name; when set with —gitops-repository, the generated upcloud-cloud-provider stack is committed to Git (optional)
`--gitops-repository`		GitOps repository (e.g. org/repo) to commit the generated stack to (optional)
`--include-networking`	`true`	Install Traefik + cert-manager for ingress (default on; pass —include-networking=false to skip). Requires —external-cloud-provider (the ingress LoadBalancer is provisioned by the cloud controller manager)
`--kubernetes-version`		Kubernetes version (optional; see `ankra cluster k3s-versions` or `ankra cluster kubeadm-versions`)
`--name`		Cluster name (required)
`--network-ip-range`	`10.0.0.0/16`	Network IP range
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--ssh-key-credential-id`		SSH key credential ID (required)
`--worker-count`	`1`	Number of worker nodes
`--worker-plan`	`2xCPU-4GB`	Worker plan
`--zone`		UpCloud zone (required)

ankra cluster upcloud k8s-version

Get current Kubernetes version for an UpCloud cluster

ankra cluster upcloud k8s-version <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster upcloud node-group

List, add, scale, upgrade, and delete node groups.

ankra cluster upcloud nodes

ankra cluster upcloud nodes get

Show full spec and metadata for a single node

ankra cluster upcloud nodes get <cluster_id> <node_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster upcloud nodes list

List all nodes for the cluster

ankra cluster upcloud nodes list <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster upcloud nodes restart

ankra cluster upcloud nodes restart <cluster_id> <node_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster upcloud start

Start (re-provision) a stopped UpCloud cluster. Use —scope control_plane to bring up only the control plane.

ankra cluster upcloud start <cluster_id> [flags]

Flags

Flag	Default	Description
`--scope`	`all`	Provisioning scope: ‘all’ or ‘control_plane’

ankra cluster upcloud stop

Stop an UpCloud cluster’s compute while keeping its configuration so it can be started again later. —force also deletes the cluster’s CSI storage volumes and load balancers, which otherwise keep billing while the cluster is stopped - the persisted data is lost.

ankra cluster upcloud stop <cluster_id> [flags]

Flags

Flag	Default	Description
`--force`	`false`	Also delete the cluster’s CSI storage volumes and load balancers (destroys persisted data; they otherwise keep billing while stopped)

ankra cluster upcloud workers

Get current worker count for an UpCloud cluster

ankra cluster upcloud workers <cluster_id> [flags]

Flags

Flag	Default	Description
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster upgrade

Upgrade the Kubernetes version on all nodes in a cloud cluster. The cloud provider (Hetzner, OVH, UpCloud, DigitalOcean, Proxmox VE, or HPE Morpheus) is detected automatically from the cluster, so you do not need to remember which provider it runs on. Both k3s and kubeadm clusters are supported; list the available target versions with ‘ankra cluster k3s-versions’ or ‘ankra cluster kubeadm-versions’. Nodes upgrade one at a time (control plane first, then workers): each node is cordoned, drained respecting PodDisruptionBudgets, upgraded, and gated on being Ready at the target version before the rollout moves on. An etcd snapshot is taken before the control plane upgrade. A drain blocked by a PodDisruptionBudget aborts the rollout; pass —force to proceed anyway. Downgrades and skipping minor versions are not supported. Examples: ankra cluster upgrade 62f4559a-a44d-46d7-aab3-a57c9dd6b4c6 v1.36.1+k3s1 ankra cluster upgrade 62f4559a-a44d-46d7-aab3-a57c9dd6b4c6 v1.33.2 # kubeadm

ankra cluster upgrade <cluster_id> <target_version> [flags]

Flags

Flag	Default	Description
`--force`	`false`	proceed even when a node drain is blocked (bypasses PodDisruptionBudget failures)

ankra cluster validate

Validate an ImportCluster YAML file. The local structural, dependency, and YAML checks run first (the same ones as ‘ankra cluster apply —dry-run’), then the file is sent to the Ankra API for server-side validation that the offline checks cannot perform:

chart existence in the Helm registries connected to your organisation
plaintext Kubernetes Secret / unencrypted addon value detection
parent references resolved against a cluster’s existing resources

Nothing is applied. Use —cluster <id> to validate the spec against an existing cluster’s deployed resources, and —strict-secrets to treat plaintext secrets as errors instead of warnings.

ankra cluster validate [flags]

Flags

Flag	Default	Description
`--cluster`		Validate against an existing cluster’s resources (cluster ID)
`-f`, `--file`		Path to the ImportCluster YAML file to validate
`-o`, `--output`		Output format: json or yaml (default: human-readable)
`--strict-secrets`	`false`	Treat plaintext secrets as errors instead of warnings

ankra cluster variables

Manage cluster-scoped variables that are available to every stack on the cluster as template substitutions in manifests and addon values. Cluster variables shadow organisation variables of the same name on this cluster. ankra cluster variables list ankra cluster variables get DB_HOST —cluster prod ankra cluster variables set DB_HOST db.prod.example.com ankra cluster variables delete DB_HOST When —cluster is omitted, the active selection is used.

ankra cluster variables delete

Delete a cluster variable

ankra cluster variables delete <name> [flags]

Flags

Flag	Default	Description
`--cluster`		Target cluster (name or ID); defaults to the active selection
`--yes`	`false`	Skip the confirmation prompt

ankra cluster variables get

Get a single cluster variable

ankra cluster variables get <name> [flags]

Flags

Flag	Default	Description
`--cluster`		Target cluster (name or ID); defaults to the active selection
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster variables list

List variables for a cluster

ankra cluster variables list [flags]

Flags

Flag	Default	Description
`--cluster`		Target cluster (name or ID); defaults to the active selection
`-o`, `--output`		Output format: json or yaml (default: human-readable)

ankra cluster variables set

Create or update a cluster variable (upsert). The value can be read from stdin by passing ”-”.

ankra cluster variables set <name> <value> [flags]

Flags

Flag	Default	Description
`--cluster`		Target cluster (name or ID); defaults to the active selection
`--description`		Optional human-readable description

​ankra cluster

​ankra cluster access

​ankra cluster access grant

​ankra cluster access list

​ankra cluster access revoke

​ankra cluster addons

​ankra cluster addons available

​ankra cluster addons list

​ankra cluster addons settings

​ankra cluster addons uninstall

​ankra cluster addons update

​ankra cluster addons upgrade

​Bump chart version

​Tweak a single Helm values field with —set (mutates the existing values)

​Address a list item by a field instead of an index

​Replace the whole values document

​ankra cluster addons values

​ankra cluster agent

​ankra cluster agent status

​ankra cluster agent token

​ankra cluster agent upgrade

​ankra cluster apply

​ankra cluster clear

​ankra cluster clone

​ankra cluster decrypt

​ankra cluster decrypt addon

​ankra cluster decrypt manifest

​Cluster mode against the selected cluster

​Cluster mode against a specific cluster

​File mode

​ankra cluster deprovision

​ankra cluster digitalocean

​ankra cluster digitalocean bastion

​ankra cluster digitalocean bastion resize

​ankra cluster digitalocean control-plane

​ankra cluster digitalocean control-plane get

​ankra cluster digitalocean control-plane set-count

​ankra cluster digitalocean control-plane set-instance-type

​ankra cluster digitalocean create

​ankra cluster digitalocean k8s-version

​ankra cluster digitalocean node-group

​ankra cluster digitalocean nodes

​ankra cluster digitalocean nodes get

​ankra cluster digitalocean nodes list

​ankra cluster digitalocean nodes restart

​ankra cluster digitalocean regions

​ankra cluster digitalocean sizes

​ankra cluster digitalocean start

​ankra cluster digitalocean stop

​ankra cluster digitalocean workers

​ankra cluster domain

​ankra cluster draft

​ankra cluster encrypt

​ankra cluster encrypt addon

​Cluster mode against the selected cluster

​Cluster mode against a specific cluster, disambiguating stack

​Encrypt several keys in one run

​File mode

​ankra cluster encrypt manifest

​Cluster mode against the selected cluster

​Cluster mode against a specific cluster

​Set a new value and encrypt it atomically (single commit, no plaintext)

​Encrypt several keys in one run

​Encrypt every data/stringData key of a Secret manifest

​File mode

​ankra cluster get

​ankra cluster get configmaps

​ankra cluster get cronjobs

​ankra cluster get daemonsets

​ankra cluster get deployments

​ankra cluster get events

​ankra cluster get ingresses

​ankra cluster get k8s-jobs

​ankra cluster get namespaces

​ankra cluster get nodes

​ankra cluster get pods

​ankra cluster get resources

​ankra cluster get secrets

​ankra cluster get services

​ankra cluster get statefulsets

ankra cluster

ankra cluster access

ankra cluster access grant

ankra cluster access list

ankra cluster access revoke

ankra cluster addons

ankra cluster addons available

ankra cluster addons list

ankra cluster addons settings

ankra cluster addons uninstall

ankra cluster addons update

ankra cluster addons upgrade

Bump chart version

Tweak a single Helm values field with —set (mutates the existing values)

Address a list item by a field instead of an index

Replace the whole values document

ankra cluster addons values

ankra cluster agent

ankra cluster agent status

ankra cluster agent token

ankra cluster agent upgrade

ankra cluster apply

ankra cluster clear

ankra cluster clone

ankra cluster decrypt

ankra cluster decrypt addon

ankra cluster decrypt manifest

Cluster mode against the selected cluster

Cluster mode against a specific cluster

File mode

ankra cluster deprovision

ankra cluster digitalocean

ankra cluster digitalocean bastion

ankra cluster digitalocean bastion resize

ankra cluster digitalocean control-plane

ankra cluster digitalocean control-plane get

ankra cluster digitalocean control-plane set-count

ankra cluster digitalocean control-plane set-instance-type

ankra cluster digitalocean create

ankra cluster digitalocean k8s-version

ankra cluster digitalocean node-group

ankra cluster digitalocean nodes

ankra cluster digitalocean nodes get

ankra cluster digitalocean nodes list

ankra cluster digitalocean nodes restart

ankra cluster digitalocean regions

ankra cluster digitalocean sizes

ankra cluster digitalocean start

ankra cluster digitalocean stop

ankra cluster digitalocean workers

ankra cluster domain

ankra cluster draft

ankra cluster encrypt

ankra cluster encrypt addon

Cluster mode against the selected cluster

Cluster mode against a specific cluster, disambiguating stack

Encrypt several keys in one run

File mode

ankra cluster encrypt manifest

Cluster mode against the selected cluster

Cluster mode against a specific cluster

Set a new value and encrypt it atomically (single commit, no plaintext)

Encrypt several keys in one run

Encrypt every data/stringData key of a Secret manifest

File mode

ankra cluster get

ankra cluster get configmaps

ankra cluster get cronjobs

ankra cluster get daemonsets

ankra cluster get deployments

ankra cluster get events

ankra cluster get ingresses

ankra cluster get k8s-jobs

ankra cluster get namespaces

ankra cluster get nodes

ankra cluster get pods

ankra cluster get resources

ankra cluster get secrets

ankra cluster get services

ankra cluster get statefulsets