Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Typo in management client error message #2457

Open
marcoderama opened this issue Feb 6, 2025 · 0 comments · May be fixed by #2458
Open

Typo in management client error message #2457

marcoderama opened this issue Feb 6, 2025 · 0 comments · May be fixed by #2458
Labels

Comments

@marcoderama
Copy link

What happened?

I was fumbling around trying to understand how to connect to my new-fangled vcluster. In the process, I tried the vcluster platform list command:

$ vcluster platform list vclusters
14:09:43 fatal create mangement client: not logged in, please make sure you have run 'vcluster platform start' to create one or 'vcluster login [vcluster-pro-url]' if one already exists

Notice that the word "management" is misspelled.

What did you expect to happen?

"management" to be spelled correctly.

How can we reproduce it (as minimally and precisely as possible)?

I had vcluster running in minikube. When minikube needed to be (re)started, I was getting this response when running vcluster platform list vclusters. (I get the same response now that minikube has been started and the vcluster is running. I suspect I shouldn't be using vcluster platform list vclusters at all. Would still be an "issue" for someone that does know what they're doing... :-)

Anything else we need to know?

First time for creating a vcluster issue. Please let me know if I've missed any of the protocols.

Host cluster Kubernetes version

$ kubectl version
Client Version: v1.32.1
Kustomize Version: v5.5.0
Server Version: v1.32.0

vcluster version

$ vcluster --version
vcluster version 0.22.4

VCluster Config

# My vcluster.yaml / values.yaml here
@marcoderama marcoderama linked a pull request Feb 6, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant