[k8s plugin] Clusters view is empty
See original GitHub issueDescribe the bug
Clusters
view from Kubernetes plugin is empty although kubeconfig is set up correctly, see the terminal output
Che version
- latest
- nightly
- other: please specify
Steps to reproduce
- Run a workspace with the latest version of Kubernetes plugin.
- Inject kubeconfig into the running workspace with
chectl workspace:inject -k
command. - Refresh the tree. It’s empty although
kubectl get po
output shows that kubeconfig has correct configuration.
Expected behavior
Clusters
tree should display clusters objects.
Runtime
- kubernetes (include output of
kubectl version
) - Openshift (include output of
oc version
) - minikube (include output of
minikube version
andkubectl version
) - minishift (include output of
minishift version
andoc version
) - docker-desktop + K8S (include output of
docker version
andkubectl version
) - other: (please specify)
Screenshots
Installation method
- chectl
- che-operator
- minishift-addon
- I don’t know
Environment
- my computer
- Windows
- Linux
- macOS
- Cloud
- Amazon
- Azure
- GCE
- other (please specify)
- other: please specify
Additional context
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
vs-kubernetes settings empty and I can't see anything in the ...
My current kubernetes plugin was working and showed all my clusters but recently they all disappeared. I have tried uninstalling and ...
Read more >Add Existing Cluster fails with blank page · Issue #996 - GitHub
When adding an existing cluster, this allows you to select cluster type, and then subscription, however the following page is blank:
Read more >Troubleshooting CNI plugin-related errors - Kubernetes
To fix this issue, update your CNI plugins and CNI config files. Failed to destroy network for sandbox error. If the version of...
Read more >Kubernetes | Jenkins plugin
Jenkins plugin to run dynamic agents in a Kubernetes cluster. ... Tested with jenkins/inbound-agent , see the Docker image source code.
Read more >Configuring Kubernetes integration - Backstage.io
A name to represent this cluster, this must be unique within the clusters array. Users will see this value in the Software Catalog...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I confirm that it is fixed. note for self, need to inject kubeconfig using
chectl server:inject
or for now when being in multiuser (until this issue fixed): 1/ Copy your local kubeconfig to the clipboard. Use kubectl config view --raw --flatten --minify to get it. 2/ Paste the copied kubeconfig into the ~/.kube/config file into plugin sidecar (Right menu My Workspace -> Plugins -> vscode-kubernetes-xxx -> New Terminal) (can use vi to create the file content) 3/ Refresh Clusters tree with Refresh button@apupier just make sure that your workspace is started with the
next
versions of Che Theia and K8s plugin images. If you deleted your minikube, obviously the newest images have to be downloaded.I’ve also checked it on my minikube. Probably it’s really fixed by https://github.com/eclipse/che-theia/pull/468