-
Notifications
You must be signed in to change notification settings - Fork 60
Cannot login if my kube config doesn't exist #3872
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
Comments
I tried to reproduce this and the login succeeded. |
Same here |
The issue is still reproducible when running the extension deployed to a cluster. It still fails with Can be reproduced with the project described in eclipse-che/che#23183 |
vrubezhny
added a commit
to vrubezhny/vscode-openshift-tools
that referenced
this issue
Nov 29, 2024
Creates a minimalistic Kube config file in `~/.kube/` directory needed for `@kubernetes/client-node` API. The file contents doesn't define any clusters/users/contexts/etc. properties. Fixes: redhat-developer#3872 Signed-off-by: Victor Rubezhny <[email protected]>
datho7561
pushed a commit
that referenced
this issue
Nov 29, 2024
Creates a minimalistic Kube config file in `~/.kube/` directory needed for `@kubernetes/client-node` API. The file contents doesn't define any clusters/users/contexts/etc. properties. Fixes: #3872 Signed-off-by: Victor Rubezhny <[email protected]>
vrubezhny
added a commit
to vrubezhny/vscode-openshift-tools
that referenced
this issue
Nov 29, 2024
…configured Prevents the extension activation failure in case of 'KUBECONFIG' variable doesn't contain any existing Kubernetes configuraion file set. Issue: redhat-developer#3872 Signed-off-by: Victor Rubezhny <[email protected]>
vrubezhny
added a commit
to vrubezhny/vscode-openshift-tools
that referenced
this issue
Nov 29, 2024
…configured Prevents the extension activation failure in case of 'KUBECONFIG' variable doesn't contain any existing Kubernetes configuration file set. Issue: redhat-developer#3872 Signed-off-by: Victor Rubezhny <[email protected]>
vrubezhny
added a commit
to vrubezhny/vscode-openshift-tools
that referenced
this issue
Nov 29, 2024
…configured Prevents the extension activation failure in case of 'KUBECONFIG' variable doesn't contain any existing Kubernetes configuration file set. Issue: redhat-developer#3872 Signed-off-by: Victor Rubezhny <[email protected]>
vrubezhny
added a commit
to vrubezhny/vscode-openshift-tools
that referenced
this issue
Nov 29, 2024
…configured Prevents the extension activation failure in case of 'KUBECONFIG' variable doesn't contain any existing Kubernetes configuration file set. Issue: redhat-developer#3872 Signed-off-by: Victor Rubezhny <[email protected]>
vrubezhny
added a commit
that referenced
this issue
Nov 29, 2024
…configured Prevents the extension activation failure in case of 'KUBECONFIG' variable doesn't contain any existing Kubernetes configuration file set. Issue: #3872 Signed-off-by: Victor Rubezhny <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
rm ~/.kube/config
)EXPECTED: you are presented with the login dialog
ACTUAL: you are presented with an error saying the kubeconfig doesn't exist
The text was updated successfully, but these errors were encountered: