Editing YAML and applying

New is always better. Except in production.

Barney Kube · your cluster's wingman

Edit and apply

Edit YAML… (the pencil in the detail header, or the row's actions menu) opens the object's manifest:

• managedFields is hidden and keys follow kubectl's order;
• status and the other fields the server owns are left to the server.

Make your change, open Diff to see exactly what changed against the original, then Apply. Barney sends the object back to the API (a PUT), and the list updates live as the cluster catches up.

If someone changed the object since you opened it, the API refuses with a conflict and Barney tells you, instead of overwriting their change. If you leave the editor with changes you have not applied, for example by selecting another object, Barney copies your YAML to the clipboard so you do not lose it.

The Playbook

The Dress Rehearsal

Edit the YAML, review the diff against the original, then apply. No surprises.

Copy an apply-ready manifest

Copy as apply-ready YAML copies the object without status and server bookkeeping, ready for kubectl apply -f somewhere else, like another cluster or a repository.

Secrets

A Secret's values stay masked in the editor until you reveal them for that object. See Secrets.