This repository has been archived by the owner on Dec 13, 2023. It is now read-only.
Generate more helpful context name in kubeconfig #26
Labels
component/kubify
Kubify
kind/enhancement
Enhancement, improvement, extension
lifecycle/rotten
Nobody worked on this for 12 months (final aging stage)
status/accepted
Issue was accepted as something we need to work on
Hi,
I have a command prompt that shows the currently targeted K8s cluster context, but the kubify clusters show only as USER@CLUSTER_NAME where the user is always
admin
anyways and the CLUSTER_NAME is not the full cluster name, but only a part of it (e.g.garden
) and the second important half of it is missing (e.g.dev
orstaging
).Just from where I stand (my PoV only here), a context name like CLUSTER_NAME-CLUSTER_TYPE would be more helpful (as we use kubify right now). Then I would see
garden-dev
or garden-staginginstead of
admin@gardenand
admin@garden`.Speaking of, why is there the
cluster_type
at all? I see it only referenced as part of the domain, which is maybe anyhow somewhat confusing, isn't it? So maybe it's also an option to merge it into the name and drop it altogether.Then the remaining question is whether we can drop the user from the context name, because it's hardcoded anyways, which explains why it isn't helping me in the command prompt (that I naturally try to keep small).
Thanks for considering the above, Vedran
The text was updated successfully, but these errors were encountered: