Given an existing cluster, is there any way to check
A) whether a local registry is enabled for that cluster, and
B) the value of registry-port/registry-name?

Relatedly: given a cluster that was started without the --enable-registry flag, is there any way to enable the registry post-facto?

Some clusters can be stopped when k3x is started. Users could think the current cluster should be ready, but they would really need to "start" it. We should show a warning saying something like "the current cluster is stopped".

Describe the solution you'd like:
When showing usage for a command we should show examples of the command. Like kubectl:

Why do you want this feature:
This would show user common scenarios