On this page
Install tools and add-ons
Select platform tools in the ClusterPilot Add-on Catalog, review dependencies and preflight, confirm installation and verify readiness.
These steps match the existing self-hosted product interface. An enabled workspace and suitable permissions are required.
Before you start
You need an existing cluster in ReadyForAddons, access to its Add-ons view and an authorized role. The catalog uses configured platform registry and immutable package evidence; a tool is installable only when its dependencies and backend checks pass.
1. Choose an add-on
Open Clusters → your cluster → Install Add-ons (/clusters/{id}/addons). Read the catalog row before selecting: version, install type, default namespace, dependencies, conflicts, image inventory, chart manifest, storage, network and policy notes. Select only the capabilities you need; ClusterPilot calculates the installation order for the selected add-ons.
| If you need | Check before selection |
|---|---|
| Ingress / external traffic | Domain, DNS, load-balancer path and certificate ownership. |
| Monitoring or logging | Resource overhead, retention, access and alert ownership. |
| Storage / registry | Persistent volume support, image source and data lifecycle. |
2. Start the controlled installation
- 01
Select and review
Tick the catalog items and review Installation order, dependencies, conflicts and platform image-pack readiness. Already installed items are excluded from new plans.
- 02
Create plan and preflight
Choose Install selected add-ons. ClusterPilot creates an Add-on Plan and runs preflight. The next screen is the plan detail. If gates block installation, read its errors and fix the named registry, package, dependency, permission or cluster-readiness issue.
- 03
Confirm and observe
On the admissible plan detail, review the final selection and confirm installation. Follow the OperationRun and return to Installed and planned add-ons. Verify the current version and observed readiness of the component, not just that the plan was accepted.
Platform add-on or your application?
Catalog add-ons are platform components managed by Add-on Plans. Deploy your own chart via Clusters → your cluster → Helm Releases instead. The Workloads view lists Deployments, Pods, Services and Ingresses for inspection; it is not a general image-upload screen.
3. If installation is blocked
- ✓ReadyForAddons missing: return to the cluster operation and verify Core and node readiness.
- ✓Image inventory or chart manifest missing: ask the operator to provide the versioned platform package and registry evidence.
- ✓Dependency or conflict: adjust the selection and create a new reviewed plan. Do not bypass preflight with an arbitrary manifest.
Screens and fields were checked against the ClusterPilot product code. Availability and provider ownership depend on your installation or agreement.