fix: Updating path for kubeconfig

[konstructcarrie]

Description

Updating path to correct path for export for Kubeconfig

Related Issue(s)

#854

How to test

Verify changes appear where expected

[mrsimonemms]

Strictly speaking, the path is ~/.k1/<cluster-name>/kubeconfig. I think it's ok to use ~/.k1/kubefirst/kubeconfig because we only ever use kubefirst as the cluster name in the docs, but might need an explanatory note.

[konstructcarrie]

Strictly speaking, the path is ~/.k1/<cluster-name>/kubeconfig. I think it's ok to use ~/.k1/kubefirst/kubeconfig because we only ever use kubefirst as the cluster name in the docs, but might need an explanatory note.

What's the scenario where a user might see a different path? For example if I were to write a note I'd say something like.

This path can also be ~/.k1/<cluster-name>/kubeconfig if you've modified the cluster name during x,y.z, or in such and such file.

[mrsimonemms]

@konstructcarrie the path will be whatever the given cluster-name is. By default, it's kubefirst but the CLI has a --cluster-name flag that can be provided (the Marketplace/UI installers also allow it to be configured).

My suggestion would be to use ~/.k1/kubefirst/kubeconfig as you have done and add an explanatory note. I also think one could justify not adding the note for the sake of clarity. My suggested note would be:

The default name for the management cluster is kubefirst. If you change the cluster name, the path will be updated to ~/.k1/<cluster-name>/kubeconfig.

[konstructcarrie]

@johndietz Circling back to this, where did we land on how we wanted to address this. I've lost track.