-
-
Notifications
You must be signed in to change notification settings - Fork 93
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
cloud add command fails, if ~/.kube/ does not exits #888
Comments
Indeed it is a bug, a method to initialize kubeconfig should be added when ~/.kube/ does not exist. |
@sunny0826 I'll try to help here :) I think I could use it here (probably will need small adjustments |
@AdamRussak Thanks |
i started working on it. @sunny0826 if you want to see if I'm in the right direction feel free to take a look :| |
@AdamRussak I don't see an e2e error reported in #967, do you mean to add an e2e test for this feature? |
…#967) * add create kubeconfig file * improve logic to craate default path config * revert dir check for merge * removed a func that is not used * added unit tests * fix unit tests
This issue has been fixed in v0.30.0. |
Describe the bug
cloud add command fails, if ~/.kube/ does not exits
To Reproduce
Steps to reproduce the behavior:
kubecm cloud add
Expected behavior
No error
Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: