Failed to get /version for clusterId=REDACTED: Unauthorized
Opened this issue · 3 comments
Describe the bug
I'm running an Azure Kubernetes Service cluster that recently started throwing the error Failed to get /version for clusterId=REDACTED: Unauthorized. Restarting the bored-agent temporarily fixes the issue. There's no errors or warnings in the logs of the bored agent, so troubleshooting is difficult
To Reproduce
Steps to reproduce the behavior:
- Spin up an AKS Cluster on Azure
- Install Lens agent
- Attempt to connect to the AKS cluster via the Lens Agent (not kubeconfig)
- See error
Expected behavior
When I attempt to connect to a cluster, it should connect
Screenshots
Environment (please complete the following information):
- Lens Version: 2024.7.161041-latest
- OS: Windows 11
- Installation method (e.g. snap or AppImage in Linux): exe
Logs:
When you run the application executable from command line you will see some logging output. Please paste them here:
info: ▪ [KUBE-AUTH-PROXY]: found port=63225 +200ms
info: ▪ [PRESENCE-CLIENT]: connected to presence socket https://us.bored.k8slens.dev/REDACTED +830ms
info: ▪ [TUNNEL-CLIENT]: connected to tunnel server https://us.bored.k8slens.dev/REDACTED +1ms
info: ▪ [PRESENCE-CLIENT]: presence socket message for cluster REDACTED: {"presence":{"userIds":["michaelteixeira","jdgiddings"]}} +1ms
error: ▪ [CLUSTER]: Failed to connect to "AspenAKSCluster": Error: Failed to get /version for clusterId=REDACTED: Unauthorized +630ms
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.
N/A. Using Lens Spaces
Hello @jdgiddings , thank you for reaching out i have contacted our development team regarding your issue .
Hi, could you open a support ticket for this? We could then check our backend logs for possible errors.
@panuhorsmalahti Support request submitted