rancher

--api-port seems the only way to change the clusters.cluster.server: server name in the kubeconfig. However, the port is forced and server name is optional. I'd like the ability to set the hostname without having to also set the port. This would be to preserve the random port created.

As mentioned in discord I would recommend adding the following to your k3s deployment. I see multiple pages about the k3s deployment and each are missing the following which will make sure the nodes stay alive even if you over provision pods.

INSTALL_K3S_EXEC= ........ --kubelet-arg system-reserved=cpu=100m,memory=100Mi --kubelet-arg kube-reserved=cpu=200m,memory=400Mi

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