The catalog of extensions for Sextant, the free Kubernetes desktop client. Sextant reads index.json from this repository and shows it under Settings → Extensions → Catalog. The design is in ADR-0130.
To add an extension, see CONTRIBUTING.md.
- Each extension is one reviewed file,
extensions/<id>.json. It names the extension, its GitHub repository and the publisher's minisign public key. - A workflow of this repository writes
index.json; nobody edits it by hand. For each entry it reads the newest release of the publisher's repository, verifies the signature of<id>-<version>.sextant-extwith the entry's key, checks the manifest, and records the version, size, SHA-256 and the permissions the extension asks for. - Sextant downloads the package from the publisher's release and verifies the size, the SHA-256 and the signature itself before it shows the usual consent screen. The publisher's key is pinned at install: an update signed with another key is refused.
Sextant's own extensions (Rook Ceph, sextant.rook-ceph, and, since Sextant 0.30, the tool views that moved out of
Sextant's core: Flux, Argo CD, Argo Rollouts and Workflows, cert-manager, Trivy, KEDA, Karpenter and the others, all
named sextant.<name>) keep their source in extensions/ of
the Sextant repository and are released here, on their own versions: the Release a Sextant extension workflow
(run by hand) builds one at a Sextant commit, signs it with the key in keys/sextant-extensions.pub, checks
the signature and publishes the release <extension>-v<version>. Their entries name this repository and that key.
The catalog tells you who publishes an extension and that the package you install is theirs. It does not audit the code of every release. What an extension can do is limited by Sextant's sandbox and by the permissions you grant on the consent screen.
MIT or Apache License 2.0, as Sextant: LICENSE-MIT, LICENSE-APACHE.