This message was deleted.

That command creates a kubernetes secret called

kubeconfig

in the default namespace. The contents of the secret will be the contents of the k3s.yaml file. It's not something I've ever needed, or seen done by anyone else.

Can't say it makes much sense either, you would need a valid kubeconfig to get it out again ... one case might be where you have one "main" kubernetes cluster, and store kubeconfigs for other clusters in the main cluster, but that's fairly unconventional I would say.

In case anyone was curious why I needed this, I guess this is the path the team has chosen for implementing argo.