Open the cluster → Addons tab in my.cubepath.com.
A catalog of components you can install into the cluster with one click, instead of finding the right Helm chart and getting its values right yourself. Search the catalog or filter by category or status, and use the Docs link on each entry for its own documentation.
Install and uninstall
Install runs the installation in the background — the add-on's status updates as it progresses. If it fails, Retry re-runs it.
Uninstall removes the add-on from the cluster and can't be undone.
NoteUninstalling removes the add-on's workloads, not necessarily the data or resources it created. An add-on that provisioned persistent volumes or load balancers may leave them behind — check before you assume it's all gone.
The two you'll almost certainly want
An ingress controller. A fresh cluster has no public entry point. An ingress controller is what turns Ingress resources into actual routing, and it's the first half of exposing your apps — the second half is a load balancer in front of it.
Metrics. The cluster has no built-in metrics pipeline. Install Metrics Server for the basics — it's what makes kubectl top and the Horizontal Pod Autoscaler work — or the Prometheus Stack for full monitoring with Grafana dashboards. See Metrics.
TipInstall add-ons through this tab rather than by hand with Helm where both are possible. The dashboard tracks what's installed and its state; a chart you installed yourself is invisible here.