Appearance
Tool integrations
Add a cluster once. Plous uses that connection for Kubernetes and any detected Helm, Argo CD, or Flux tools.
Current capabilities
| Tool | Operations | Guide |
|---|---|---|
| Kubernetes | Browse resources, events, logs, metrics, and YAML. Edit, scale, restart, delete, or open a container terminal. | Kubernetes |
| Helm | Read releases and revisions, compare configuration, preview charts, and roll back | Helm |
| Argo CD | Read Applications, ApplicationSets, Projects, and their reported status | Argo CD |
| Flux | Read Kustomizations, HelmReleases, Sources, and reconciliation status | Flux |
What can change the cluster?
Kubernetes actions and container terminals can make changes. Helm rollback requires a preview and confirmation. Chart previews do not install or upgrade anything.
Argo CD and Flux views are read-only. Agent tools also read by default. Active diagnostics can explicitly enable container commands or temporary tests.
Add a connection
- Select a workspace.
- Choose Monitor → + Add Context or + Add Connection → Kubernetes Cluster.
- Choose the kubeconfig file and contexts, then save.
- Select the connection and press
22for Explore.
Use Settings → Current Workspace to edit or remove connections. Removal does not delete cluster resources or edit kubeconfig.
Saved tool connections
| Required | Optional |
|---|---|
| Name and Kubernetes context | Kubeconfig path, namespace, Helm release storage, repository/cache/registry configuration paths |
Kubernetes is always available. Helm appears when release metadata is found. Argo CD and Flux appear when their APIs are discovered.
Adding a context reads local metadata without contacting the cluster. Opening its views connects. Existing separate Kubernetes and Helm records keep their identities and histories.
See connection setup and Activity.
AI and integrations
Agents use the selected cluster and its Kubernetes permissions. General chat has no live cluster tools.
See the tool reference and AI setup.