Custom resources and Helm
Custom resources
The navigator's Custom Resources section lists the API groups of the custom resource kinds the cluster's CRDs define, whether or not your role can list their objects. If you can't read CRDs, it falls back to API discovery and shows the kinds you can list instead, which may include kinds served by aggregated API servers; built-in groups such as metrics.k8s.io are never shown. Groups start collapsed; expand one to see its kinds (for example cert-manager.io → Certificate). The refresh button re-runs discovery. Click a kind to open a table of its objects in the selected namespaces, with the columns kubectl get shows for that kind, and Age. A kind's count appears once its table has been opened. The table updates live while it is open. Its details panel has Overview (including the status conditions), YAML with the same edit, diff and apply flow as built-in kinds, and Events. Custom resources are not watched for the graph, but one that owns a watched object (a Certificate owning a Secret, a Rollout owning ReplicaSets) appears there as its owner. Toggle those nodes with the Custom chip. + Create starts from a minimal manifest of the kind, and if access is lost while a table is open it shows the reason with Retry.
Helm
The Helm section opens its own view: a table of the releases in the selected namespaces, read from Helm 3's release Secrets, with chart and version, app version, revision, status and when it was last deployed. The list follows changes live, such as new revisions and status changes. Select a release to see its tabs below the table: Overview, the user-supplied Values, the History of stored revisions, the chart's Notes, and the Resources it installed that exist in the cluster; opening one of those shows it in the details panel. Its objects are highlighted on the graph, whose header reads Release web highlighted · Clear. Closing the release, Clear or switching namespaces removes the highlight. Wiring reads releases only: it never installs, upgrades or rolls back. Values can contain credentials, so Wiring never logs them. Helm's release Secrets are left out of the graph and the Secrets table. Show Helm storage in the Secrets table reveals them.