How do I name the cluster when creating server?

[YAMLcase]

I'm at a loss on how to name the cluster when running k3s server. k3d has k3d cluster create <cluster-name> so there must be some way, I just can't grok it. Thanks.

[briandowns]

Pretty sure k3d uses that as part of the docker container name / kubeconfig. When k3d starts k3s, it's running "/bin/k3s server --https-listen-port 6443".

[brandond]

Clusters don't have names, internally. You can give clusters names in your kubeconfig, but the cluster does not store its own name anywhere.

[YAMLcase]

I understand now this "cluster name" is what is used in the kubeconfig generation. Does K3s generate this kubeconfig? If so, how does it know to use "default" as the name? Can this be an option we feed to that routine? i.e. --default-name mycluster .

In my explorations last night I dug through the k3d code and got as far as cluster.Name being added to a label... but couldn't see what that was applied to. Was it even a kubernetes label? Could have been attached to the containers

[brandond]

Does K3s generate this kubeconfig?

Which kubeconfig file are you referring to?

K3s generates the admin kubeconfig at /etc/rancher/k3s/k3s.yaml. This will only ever contain a 'default' cluster entry.

K3d manages kubeconfig files in your home directory (traditionally ~/.kube/config), including adding multiple uniquely-named clusters and contexts for the clusters you create using k3d.