Integrations and extensions
Source: src/routes/cluster/HelmBrowser.tsx, src/routes/cluster/ArgocdView.tsx, src/routes/cluster/TektonView.tsx, src/routes/cluster/CrdBrowser.tsx, src-tauri/src/k8s/argocd.rs, src-tauri/src/k8s/tekton.rs at v0.18.0.
Helm is always present in the cluster sidebar. You can inspect releases and, when the required Helm tooling and permissions are available, install, upgrade, roll back, or uninstall them. Review the rendered values and target namespace before a write. Follow the Helm guide for the exact workflow and limitations.
Argo CD and Tekton
Section titled “Argo CD and Tekton”Argo CD and Tekton appear only when Lumen detects their APIs. Their screens read the corresponding custom resources from the selected cluster. Argo CD provides application and ownership views; Tekton provides pipeline and task-run views. Absence from the sidebar can mean the APIs are not installed, not discoverable, or not readable by the current identity.
Lumen does not install either controller. Reconciliation, admission, and execution remain the responsibility of the controller running in the cluster.
Custom resources
Section titled “Custom resources”Custom Resources lists discovered CRDs and their instances. Select a CRD; Lumen uses its preferred version and reads instances through the generic browser. The v0.18.0 screen does not offer a version or scope selector. It cannot promise a controller-specific status interpretation or safe mutation workflow. Use controller documentation when a field or condition is unfamiliar.
The unreleased custom-resource explorer adds served-version selection, printer columns, schema and condition inspection, and server-validated instance mutations. These are not part of v0.18.0.