You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the solution you'd like:
I think it would be helpful to have a way to display the alias details (such as what cluster they refer to).
Why do you want this feature:
I often forget exactly which cluster a particular alias is referring to and, unfortunately, the current kconnect alias ls command simply lists out the alias names without any other details. So, I end up having to delete the alias and re-associate it with my desired cluster just to be safe, since I currently have no way of confirming whether the alias is already associated with my desired cluster.
Anything else you would like to add:
Perhaps this could be implemented as an additional flag to the existing kconnect alias ls command?
The text was updated successfully, but these errors were encountered:
would using the kubectl command cluster info solve this problem?
example for a rancher connection:
$ kubectl cluster-info
Kubernetes control plane is running at https:///k8s/clusters/
CoreDNS is running at https:///k8s/clusters//api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
if that doesn't help would using the command 'kconnect to' solve this problem?
it reads the history yaml file of your previous connections.. and has data like user and cluster...
Describe the solution you'd like:
I think it would be helpful to have a way to display the alias details (such as what cluster they refer to).
Why do you want this feature:
I often forget exactly which cluster a particular alias is referring to and, unfortunately, the current
kconnect alias ls
command simply lists out the alias names without any other details. So, I end up having to delete the alias and re-associate it with my desired cluster just to be safe, since I currently have no way of confirming whether the alias is already associated with my desired cluster.Anything else you would like to add:
Perhaps this could be implemented as an additional flag to the existing
kconnect alias ls
command?The text was updated successfully, but these errors were encountered: