Notifications
When a change is done, a notification at the bottom right says what happened, in plain words: “Scaled storefront to 5 replicas”, “Cordoned worker-2”.- A notification stays for six seconds, or ten when something went wrong.
- It stays as long as the pointer is over it, so you have time to read it and act.
- Some notifications have a button: Undo, or Open for something new, like the job Run now started or the objects Create from YAML made.
Undo
Undo in a change’s notification makes the opposite change. It’s a change like any other: it has its own command, and its own line in the Activity log.
If the undo fails (someone changed the object in between, say), a notification says “Couldn’t undo”, with the reason.
Restarts, rollbacks, drains, deletes, YAML edits and changes to several objects at once have no Undo. Restarts and rollbacks can be followed by another rollback, from Roll back…. See Actions by kind.
The Activity log
The Activity button in the header (a clock with an arrow) opens Changes this session: every change you made from KubeStacks, newest first. A count on the button shows how many are new since you last looked. Each entry shows:- What happened, like “Restarted checkout”. Choose it to open the object, when it’s in the cluster you’re looking at.
- When, and the cluster, when it’s another one than you’re looking at.
- Its status: In progress, Done or Failed, with the reason if it failed.
- The kubectl command that does the same thing, with Copy command.
The log lives only as long as the session: it’s empty again when you restart KubeStacks, or reload the page when it runs in your cluster. For a lasting record of who changed what, use the cluster’s audit log.
Changing things safely
The guard rails around every change.
Actions by kind
Everything you can do to each kind, and the options.