Connection issues when going through Teleport (kubectl works)

[Ezzahhh]

Describe the bug
When I generate a kubeconfig that goes through Teleport with tsh kube login my-cluster and then k9s I get frequent connection issues like context deadline exceeded or http2: client connection lost. k9s will successfully open but will freeze and give me these errors when trying to navigate or do anything immediately.

If I use kubectl with Teleport, there are no issues with the same kubeconfig which leads me to believe that there perhaps is something about the dial in k9s that may not be fully compatible with Teleport.

I notice that the behaviour is consistently like this but if lucky and wait for a few minutes the connection is somehow recovered and k9s is usable as normal. I understand that there may be an issue with Teleport here but I don't fully understand how k9s and kubectl are different enough to experience this issue.

To Reproduce
Steps to reproduce the behavior:

1. Generate kubeconfig with tsh kube login your-cluster
2. Run k9s
3. Try to navigate in the UI, describe or view pods logs (basically anything)

Historical Documents
When applicable please include any supporting artifacts: k9s debug logs, configurations, resource manifests, ...

4:28PM ERR Fail to load global/context configuration error="k9s config file \"/Users/ericlin/Library/Application Support/k9s/config.yaml\" load failed:\nAdditional property fullScreen is not allowed"
4:28PM DBG No custom skin found. Using stock skin
4:28PM DBG Factory START with ns `"[REDACT]"
4:28PM DBG Fetching latest k9s rev...
4:28PM DBG K9s latest rev: "v0.32.7"
4:28PM DBG No custom skin found. Using stock skin
4:29PM WRN   Dial Failed! error="Post \"https://teleport.[REDACT].com:443/apis/authorization.k8s.io/v1/selfsubjectaccessreviews\": context deadline exceeded"
4:29PM ERR Post "https://teleport.[REDACT].com:443/apis/authorization.k8s.io/v1/selfsubjectaccessreviews": context deadline exceeded
4:29PM ERR can't connect to cluster error="Get \"https://teleport.[REDACT].com:443/version?timeout=15s\": context deadline exceeded"
4:29PM ERR ClusterUpdater failed error="conn check failed (1/5)"
4:29PM ERR can't connect to cluster error="Get \"https://teleport.[REDACT].com:443/version?timeout=15s\": net/http: request canceled (Client.Timeout exceeded while awaiting headers)"
4:29PM ERR ClusterUpdater failed error="conn check failed (2/5)"
4:29PM ERR can't connect to cluster error="Get \"https://teleport.[REDACT].com:443/version?timeout=15s\": http2: client connection lost"
4:29PM ERR ClusterUpdater failed error="conn check failed (3/5)"
4:30PM ERR can't connect to cluster error="Get \"https://teleport.[REDACT].com:443/version?timeout=15s\": context deadline exceeded"
4:30PM ERR ClusterUpdater failed error="conn check failed (1/5)"
4:30PM ERR can't connect to cluster error="Get \"https://teleport.[REDACT].com:443/version?timeout=15s\": http2: client connection lost"
4:30PM ERR ClusterUpdater failed error="conn check failed (2/5)"
4:31PM ERR can't connect to cluster error="Get \"https://teleport.[REDACT].com:443/version?timeout=15s\": context deadline exceeded"
4:31PM ERR ClusterUpdater failed error="conn check failed (3/5)"
4:32PM ERR can't connect to cluster error="Get \"https://teleport.[REDACT].com:443/version?timeout=15s\": net/http: request canceled (Client.Timeout exceeded while awaiting headers)"
4:32PM ERR ClusterUpdater failed error="conn check failed (1/5)"
4:33PM ERR can't connect to cluster error="Get \"https://teleport.[REDACT].com:443/version?timeout=15s\": http2: client connection lost"
4:33PM ERR ClusterUpdater failed error="conn check failed (2/5)"

Expected behavior
K9s should have no issues to connect to the cluster consistently like kubectl.

Screenshots
If applicable, add screenshots to help explain your problem.

Versions (please complete the following information):

• OS: [e.g. OSX] macOS 15.2
• K9s: [e.g. 0.1.0] v0.32.7
• K8s: [e.g. 1.11.0] 1.29

Additional context
Add any other context about the problem here.