Skip to main content

ankra helm

Commands to manage Helm chart registries and registry credentials.

ankra helm addon-catalog

The add-on-first view of the organisation’s charts: one entry per add-on definition with the charts that match it and how many clusters run it, plus an entry for each chart no definition matches.

ankra helm addon-catalog get

Show one add-on of the catalog: its charts and the clusters that run it
Examples
Flags

ankra helm addon-catalog list

List one page of the add-on catalog. --search, --category, --source and --connected narrow it; --types takes the comma-separated entry types to include (name manifest_addon to receive manifest add-ons). -o json prints the platform’s page with its pagination and category facet.
Examples
Flags

ankra helm addon-definitions

An add-on definition describes one add-on (its name, description, links and category) and which charts it matches: by chart name, by chart keyword and by the prefix of a chart’s home URL. The add-on catalog groups the organisation’s charts under the definitions that match them. The organisation sees Ankra’s global definitions and its own. Ankra’s are read-only; changing or deleting one is refused (403). A chart link is a manual override: it includes a chart the rules miss, or excludes one they match.

ankra helm addon-definitions create

Create an add-on definition for the organisation. <name> is a lowercase slug (letters, digits and dashes). The match rules say which charts the catalog groups under the add-on: any chart whose name, keyword or home URL prefix matches. A name already in use is refused (409).
Examples
Flags

ankra helm addon-definitions delete

Delete an organisation add-on definition. The charts it grouped stay in their registries and installed add-ons keep running; the catalog just stops grouping them under it. It asks first; --yes skips the question and is required when there is no terminal to ask on. Ankra’s global definitions are read-only (403).
Examples
Flags

ankra helm addon-definitions get

Show one add-on definition with its chart links
Examples
Flags Add a manual link between one chart in one registry and an add-on definition, overriding the definition’s match rules for that chart: --type include (the default) groups a chart the rules miss under the add-on, --type exclude keeps out one they match.
Examples
Flags

ankra helm addon-definitions list

List the add-on definitions visible to the organisation
Examples
Flags Remove one manual chart link, named by its chart, registry and --type (include by default). The definition’s match rules decide for that chart again.
Examples
Flags

ankra helm addon-definitions update

Change an organisation add-on definition. Only the flags you pass change: the command reads the definition, applies them and sends the whole definition back, because the platform replaces every field on an update. A match flag replaces that whole list, and an optional text flag passed empty (--category "") clears the member. Ankra’s global definitions are read-only (403).
Examples
Flags

ankra helm credentials

Manage Helm registry credentials

ankra helm credentials create

Create a Helm registry credential with username and password. The password is prompted interactively, or read from stdin with --password-stdin so scripts and agents can create it without a terminal. Examples:
Flags

ankra helm credentials delete

Delete a Helm registry credential, addressed by its name or by the id ‘ankra helm credentials list’ prints.
Flags

ankra helm credentials get

Show a Helm registry credential by its name or by the id ‘ankra helm credentials list’ prints. The password is never returned.

ankra helm credentials list

List Helm registry credentials
Flags

ankra helm credentials update

Update a Helm registry credential’s username and password, addressed by its name or by the id ‘ankra helm credentials list’ prints. The password is prompted interactively, or read from stdin with --password-stdin. Examples:
Flags

ankra helm registries

Manage Helm chart registries

ankra helm registries create

Create a Helm chart registry from a spec file (-f, JSON or YAML) or directly from --name and --url. In a spec file the registry must be nested under exactly one of “helm_oci_registry” or “helm_http_registry”:
A flat {“name”: …, “url”: …} file is accepted and nested automatically, inferring the registry type from the URL scheme: oci:// creates an OCI registry, http:// or https:// an HTTP chart repository. The flag form uses the same inference. Examples:
Flags

ankra helm registries delete

Delete a Helm chart registry
Flags

ankra helm registries get

Get details of a Helm chart registry. The registry’s chart listing is paginated; use --page/--page-size to select which chart page the response (and -o json/yaml output) carries. Examples:
Flags

ankra helm registries list

List Helm chart registries. Results are paginated (20 per page by default). Use --search to filter by name, --page/--page-size to navigate, or --all to fetch every page. Examples:
Flags

ankra helm registries sync

Trigger a manual sync of a Helm chart registry

ankra helm registries sync-jobs

List sync jobs for a Helm chart registry
Flags

ankra helm registries update

Update a Helm chart registry
Flags