Scope of your request

Do you need...

• a new flag for a command (e.g. k3d cluster create --<your-flag>)?
  • command: delete
  • flag: config

Describe the solution you'd like

Support deleting a cluster that is defined in a config file.

Describe alternatives you've considered

Parse the config file to get the cluster name.

From my YouTube comment: https://www.youtube.com/watch?v=UoOcLXfa8EU&lc=UgwZL42zHoDLwqG-XOd4AaABAg

Can't bootstrap due to different token

Check the release notes: https://github.com/k3s-io/k3s/releases/tag/v1.21.3%2Bk3s1

⚠️ Important Upgrade Note ⚠️
If you are using K3s in a HA configuration with an external SQL datastore, and your server (control-plane) nodes were not started with t

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".

What happened:
kconnect to my-alias --password $pass -k custom/cubeconfig/path writes kubeconfig to default kubeconfig path instead of custom/cubeconfig/path

What did you expect to happen:
kconnect to respects-k --kubeconfig flag and writes to the path specified.

How to reproduce it:
touch ~/test.config
kconnect to my-alias -k ~/test.config
expect kubeconfig writes t