Best practice of setting the cluster name at deployment level about k3s HOT 4 CLOSED

We've discussed it in the past and decided against it. The admin kubeconfig really shouldn't be used for much other that locally interacting with the server. If you're managing multiple clusters to the point where you want to give their contexts unique names in your kubeconfig, you should be using more advanced tooling for that - and not using the default admin kubeconfig and admin RBAC.

from k3s.

This is a duplicate of #4610

Clusters don't know their own name, there is no field within the cluster itself to store that data. If you want the kubeconfig to reflect a different name, your best option is to make that edit when collecting the admin kubeconfig off the server nodes, or (preferably) when generating unique kubeconfigs for your users with distinct users and RBAC.

from k3s.

Thank you @brandond for providing the clarifications. I was simply trying to understand how the default value is assigned when the cluster is deployed and if there is a way to define it with a switch, during deployment. I still believe this could be an useful feature.

from k3s.

Thank you, it makes sense now.

from k3s.