rancher

Problem

I would like to be able to have different names for my node to help with discovery in tools like k9s.

If I (a) create the cluster and then (b) create the nodes I can achieve this.

But if I need to create the cluster and nodes at the same time i.e. via -agents flag then this is not possible.
And some use cases e.g. per-node volumes are only possible using this approach

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

Hello.

Although it's not documented on the official documentation https://docs.hetzner.cloud/#images , the API method only returns 25 results per page. And again, the following two GET parameters aren't documented either,
Option 1 is to raise the per_page limit such as https://api.hetzner.cloud/v1/images?per_page=50
Option 2 is to query additional pages such as https://api.hetzner.cloud/v1/

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:
Create an ARM based kconnect docker image

Why do you want this feature:
So kconnect docker images can be run on ARM machines

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]