Skip to main content

Read-only clusters

Any connected cluster can be marked Read-only. ROZOOM then only reads it: lists, details, YAML, logs and events work as usual, and anything that would change the cluster is refused.

Turn it on​

  1. Open Manage Kubernetes Clusters.
  2. On the cluster's card, tick Read-only.

The card gets a grey Read-only badge. The setting is stored per cluster and stays after a restart. Clear the box when you want to make changes again.

What is refused​

While the box is ticked, ROZOOM refuses every command that would write to the cluster through its kubectl, oc, helm and velero:

  • delete, scale, rollout restart, apply, edit and the other actions in the panels;
  • commands in a pod shell: the shell window opens, but every command in it is refused;
  • Helm installs, upgrades and uninstalls.

ROZOOM keeps a list of commands that only read. A command that is not on that list counts as a write and is refused.

Some actions, such as Scale and Delete, still open their usual dialog, and the refusal comes when you confirm. It reads like this:

[BLOCKED] [2026-11-11T07:48:09.419Z]: Cluster "minikube" is read-only. This action is not permitted.

The cluster is not changed.

What keeps working​

  • Overview, the resource lists and details, YAML view;
  • logs, events and metrics;
  • port-forward;
  • health checks (the linter).

Not an access boundary​

Read-only is a guard inside ROZOOM, not a permission on the cluster. It does not cover cloud CLIs such as aws, gcloud, az or doctl, which talk to the provider and not to the cluster. And the same kubeconfig still writes from any other tool.

For a hard limit, use RBAC: connect with credentials that the cluster itself does not allow to write.