Extensions

Extensions add integrations and extra capabilities to Kunobi beyond core Kubernetes. They are versioned independently of the app, so an extension can be updated without waiting for a new Kunobi release. Each extension has its own documentation section; this page covers installing and managing them.

Installing an Extension

1. Open Settings (⌘, / Ctrl+,) and switch to the Extensions tab.
2. The table lists both installed extensions and everything available from the catalog, with columns for Name, Publisher, Version, Source, Status, and Latest. Extensions you haven't installed yet show the status Available.
3. Select the extension's row and press Install (or press i).

The status moves through Installing... to Connected - the extension is downloaded, registered, and started automatically. No app restart is needed.

If the catalog looks stale, press Refresh Catalog (c) to force a refresh; the header shows when the catalog was last fetched.

Updating, Stopping & Removing

Select an installed extension's row to see the remaining actions in the action bar:

• Update (u) - available when the Latest column shows a newer catalog version than the one installed.
• Load (l) / Reload (r) - start an idle extension, or restart a running one.
• Stop (s) - stop a running extension without uninstalling it.
• Remove (Backspace) - stop the extension and delete it.

You can select multiple rows to install, update, or remove several extensions at once.

If an extension fails to start, its Status shows Failed or Error - hover it for the error message.

Where Extensions Appear

Each extension surfaces in the part of the app it extends. Those that connect to something outside your cluster add a source to the Sources page, where connections are added, tested and managed:

• Bitbucket adds a source to the Sources page and user group, member, repository and permission views to the Kubernetes data page. See Bitbucket.
• Cilium adds a workspace to the Kubernetes data page. See Cilium.
• Cloud Providers supplies the data behind the Cloud Providers pane on the Sources page. That pane ships with Kunobi; without the extension it shows an "extension required" notice. See Cloud Providers.
• Cloudflare adds a source to the Sources page and Cloudflare resource views to the Kubernetes data page. See Cloudflare.
• Ceph adds a workspace to the Sources page and cluster, pool, OSD and RBD views to the Kubernetes data page. See Ceph.
• RBAC adds a workspace to the Kubernetes data page showing your identity and effective permissions on the active cluster. See RBAC.
• Redfish adds a workspace to the Sources page and server views to the Kubernetes data page. See Redfish.
• SNMP adds a workspace to the Sources page and device views to the Kubernetes data page. See SNMP.

If you open one of those areas while the extension is not installed or not running, Kunobi shows an "extension required" notice with an Open Extensions button that takes you straight to the Extensions tab.

More extensions are in development.

Credentials

Extensions that need real credentials store them in your operating system's credential store, and removing a connection removes its stored secret. Three ask for none at all: Cilium and RBAC use your existing cluster connection, and Cloud Providers delegates authentication to each provider's own CLI. SNMP is the one extension that keeps its secrets in a plain-text configuration file instead. Sources covers where each kind of secret goes.