Troubleshoot Helm workflows

Where: helm. Browsing release details and history reads Helm release Secrets through Kubernetes. Install, upgrade, rollback, and uninstall use the local Helm CLI and require context protection, confirmation, the relevant Kubernetes writes, and an executable visible to the app environment.

1. Select context and namespace; inspect release status, values, manifest, notes, and history.
2. For a write, confirm the chart/version and review values and target identity.
3. Use dry-run/preflight where offered, then explicitly apply. Dry-run is not runtime-safety proof.
4. If a write fails, check CLI availability, repository/chart access, RBAC, ownership conflicts, and release status.

Source: src/routes/cluster/HelmBrowser.tsx, src-tauri/src/k8s/helm.rs, src-tauri/src/k8s/helm_cli.rs at v0.18.0.

Repository management (unreleased / main)

Not included in v0.18.0. Main commit 211f0237bcb8f59580cade245c0f50651aa8fb22 adds Helm → install → Manage Helm repositories. Add a named HTTP(S) repository, refresh indexes, search for a chart, choose a version and customize values. Continue through the existing dry-run and installation review flow; adding a repository does not install a chart.

Repository configuration belongs to the local Helm CLI and is shared across clusters on this machine. Removing an entry does not uninstall releases. Operations are serialized within Lumen and have a 60-second process timeout. Refresh reports failure if any repository fails, even when others update.

Install the Helm CLI first. Configure private-repository authentication, custom certificates and OCI registry authentication through Helm itself. The add form rejects embedded credentials, query parameters and fragments. OCI references can be entered directly in the chart field. Cluster installation and upgrade still require the usual context protection, permissions and confirmation.

Source: repository workflow, src/routes/cluster/HelmBrowser.tsx, and src-tauri/src/k8s/helm_cli.rs at the pinned main commit.