Skip to main content
Publishing an application to your organisation’s add-on catalogue snapshots its committed manifests and its deploy options as one immutable version. The add-on installs independently of the application afterwards, and keeps working even if the source application is later deleted.

What publishing does

An application in Ankra is a repository Ankra generates Kubernetes manifests for. Publishing turns the current state of those manifests into a catalogue entry your organisation can install onto any of its clusters, without going back to the application. A publish captures three things at that moment:
  • the committed manifests under the application’s manifests/ directory, plus its .ankra/ankra.yaml descriptor
  • the deploy options the application declares, which become the add-on’s install-time inputs
  • the metadata shown in the catalogue: display name, description, category
Everything is a snapshot. Later changes to the application only reach the catalogue through another publish, and published versions are immutable: a version number, once used, cannot be reused.
This is different from publishing an add-on to the Ankra catalogue. That proposes a curation manifest to the global catalogue every organisation sees, through a reviewed pull request. Publishing an application stays inside your organisation and takes effect immediately.

Publish with the CLI

The portal has no action for publishing an application or installing the result; the CLI does both.
1

Check that the application can publish

Each check reports ok, warning (publishing works, but something is worth knowing first), blocked (publishing cannot proceed until it is resolved) or unknown (the check could not be evaluated). Resolve every blocked check before you continue.
2

Publish a version

Leave out --version to take the version from the application’s descriptor. A version already published is refused. The first publish creates the add-on; later publishes add versions to it.
3

Find the add-on's id

The manifest-addon commands below take this add-on id, not the application id.

Version history

ankra application manifest-addon get <addon-id> shows the add-on’s catalogue entry, its published versions and what it declares. ankra application manifest-addon diff <addon-id> --to 1.4.0 shows what changed in a version against the one published before it (--from picks another, --path narrows it to named manifests):
  • files added, removed or modified
  • options added, removed or modified
A changed option is worth attention: options are the add-on’s install-time input contract, so changing one is a breaking change for anyone who already installed the add-on.
There is no rollback and no “current version” control. An installation pins the version it was installed at, so there is nothing to roll back to: installing an earlier version explicitly is the equivalent, and existing installations are unaffected by later publishes.

Installing a published add-on

--namespace and --version default from the add-on’s own descriptor (the newest version when you leave --version out), and each --input key=value answers a deploy option the version declares. To find manifest add-ons alongside Helm add-ons in the add-on catalogue:
Because the snapshot is self-contained, the add-on installs even when the source application has been deleted, and no new versions can be published once the source is gone.

Unpublishing and deleting

delete undeploys the workloads installed from the add-on on every cluster, not only the catalogue entry. It cannot be undone.
Both ask for confirmation; --yes skips it.

Limits

An add-on holds at most 500 published versions. Snapshots are never pruned, because installations pin the version they were installed at and removing an old snapshot would break them.