Open vandreykiv opened 3 years ago
When I connect to cluster and do vim $KUBECONFIG in terminal and replace config with one from kubeconfig file it works but after restart lens replca it back to "proxy" and we have picture as above. Could you help me understand how to fix this?
Thanks.
Is this related to #1022 and thus a duplicate of #2390?
Describe the bug When corporate proxy configured lens didn't show any information about cluster resources.
To Reproduce Steps to reproduce the behavior:
Expected behavior List of workloads, pods, deployments, etc.
Environment (please complete the following information):
Logs: When you run the application executable from command line you will see some logging output. Please paste them here:
Kubeconfig: Quite often the problems are caused by malformed kubeconfig which the application tries to load. Please share your kubeconfig, remember to remove any secret and sensitive information.