Skip to content
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

Open
vlerenc opened this issue Mar 2, 2018 · 2 comments
Open

Generate more helpful context name in kubeconfig #26

vlerenc opened this issue Mar 2, 2018 · 2 comments
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

Comments

@vlerenc
Copy link
Contributor

vlerenc commented Mar 2, 2018

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 or staging).

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 ofadmin@gardenandadmin@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

@vlerenc vlerenc added the kind/enhancement Enhancement, improvement, extension label Mar 2, 2018
@vlerenc
Copy link
Contributor Author

vlerenc commented Apr 16, 2018

I know we talked about this, but I am really concerned someone (me?) might confuse the clusters eventually and do the wrong thing to the wrong cluster if the labelling is the same for all our Kubify clusters.

@afritzler
Copy link
Contributor

Agreed! This issue should be resolved. The problem I see at the moment is, that this would cause a recreation of kubeconfig and hence the recreation of all nodes :-/ But we will definitely fix this one.

@vlerenc vlerenc added the component/kubify Kubify label Jun 27, 2018
@vlerenc vlerenc added the status/accepted Issue was accepted as something we need to work on label Aug 5, 2018
@gardener-robot-ci-1 gardener-robot-ci-1 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Oct 5, 2018
@gardener-robot-ci-1 gardener-robot-ci-1 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Dec 5, 2018
@gardener-robot-ci-1 gardener-robot-ci-1 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Feb 4, 2019
@gardener-robot-ci-1 gardener-robot-ci-1 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Apr 6, 2019
@gardener-robot-ci-1 gardener-robot-ci-1 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Jun 6, 2019
@gardener-robot-ci-1 gardener-robot-ci-1 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Aug 6, 2019
@gardener-robot-ci-2 gardener-robot-ci-2 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Oct 6, 2019
@ghost ghost added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Dec 6, 2019
@ghost ghost added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Feb 5, 2020
@ghost ghost added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Apr 6, 2020
@gardener-robot gardener-robot added lifecycle/rotten Nobody worked on this for 12 months (final aging stage) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Jun 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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
Projects
None yet
Development

No branches or pull requests

5 participants