cannot access AWS eks

[zozo6015]

Describe the bug
Cannot access AWS EKS. It doesn't want to connect on a newly installed maces Sequoia.

To Reproduce
Steps to reproduce the behavior:

1. Install lens from dmg downloaded from the website.
2. Get access to some AWS EKS clusters.
3. export the KUBECONFIG variable to the path of the kubeconfig you wanna store the kubeconfig at.
4. run aws eks update-kubeconfig --name --region
5. open Lens and browse the cluster and click on it to connect.

Expected behavior
the application would connect to the cluster and show all resources

Screenshots

Environment (please complete the following information):

• Lens Version: 2024.9.300059-latest
• OS: macOS Sequoia 15.0.1
• Installation method (e.g. snap or AppImage in Linux): dmg

Logs:
When you run the application executable from command line you will see some logging output. Please paste them here:

2024-10-14T16:58:08.617Z info: 	[INTERNAL-PROXY-MAIN]: Connection Update
2024-10-14T16:58:08.622Z error: 	[INTERNAL-PROXY-MAIN]: Connection Update
2024-10-14T16:58:08.623Z warn: 	[INTERNAL-PROXY-MAIN]: Proxy request for clusterId="7c713451c33e0926551505d9d7c47470" to url="/version" has statusCode=500
2024-10-14T16:58:08.623Z error: 	[CLUSTER-MANAGER-MAIN]: Failed to connect to clusterId="7c713451c33e0926551505d9d7c47470": Error: Failed to GET "https://127.0.0.1:52756/7c713451c33e0926551505d9d7c47470/version"
2024-10-14T16:58:08.623Z error: 	[INTERNAL-PROXY-MAIN]: Connection Update
2024-10-14T16:58:10.209Z info: 	[CLUSTER-MANAGER-MAIN]: Ensuring cluster connection is active
2024-10-14T16:58:10.210Z info: 	[INTERNAL-PROXY-MAIN]: Connection Update
2024-10-14T16:58:10.220Z error: 	[INTERNAL-PROXY-MAIN]: Connection Update
2024-10-14T16:58:10.221Z warn: 	[INTERNAL-PROXY-MAIN]: Proxy request for clusterId="7c713451c33e0926551505d9d7c47470" to url="/version" has statusCode=500
2024-10-14T16:58:10.222Z error: 	[CLUSTER-MANAGER-MAIN]: Failed to connect to clusterId="7c713451c33e0926551505d9d7c47470": Error: Failed to GET "https://127.0.0.1:52756/7c713451c33e0926551505d9d7c47470/version"
2024-10-14T16:58:10.222Z error: 	[INTERNAL-PROXY-MAIN]: Connection Update
2024-10-14T16:58:11.341Z info: 	[CLUSTER-MANAGER-MAIN]: Ensuring cluster connection is active
2024-10-14T16:58:11.341Z info: 	[INTERNAL-PROXY-MAIN]: Connection Update
2024-10-14T16:58:11.353Z error: 	[INTERNAL-PROXY-MAIN]: Connection Update
2024-10-14T16:58:11.354Z warn: 	[INTERNAL-PROXY-MAIN]: Proxy request for clusterId="7c713451c33e0926551505d9d7c47470" to url="/version" has statusCode=500
2024-10-14T16:58:11.355Z error: 	[CLUSTER-MANAGER-MAIN]: Failed to connect to clusterId="7c713451c33e0926551505d9d7c47470": Error: Failed to GET "https://127.0.0.1:52756/7c713451c33e0926551505d9d7c47470/version"
2024-10-14T16:58:11.355Z error: 	[INTERNAL-PROXY-MAIN]: Connection Update

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.

apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: <certificate>
    server: https://<randomstring>.gr7.us-east-2.eks.amazonaws.com
  name: <clustername>
contexts:
- context:
    cluster: qa-eks
    user: qa-eks
  name: qa-eks
current-context: qa-eks
kind: Config
preferences: {}
users:
- name: <arn>
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1beta1
      args:
      - --region
      - us-east-2
      - eks
      - get-token
      - --cluster-name
      - qa-eks
      - --output
      - json
      command: aws
      env:
      - name: AWS_PROFILE
        value: <profilename>
      interactiveMode: IfAvailable
      provideClusterInfo: false

[clrothmann]

@zozo6015 Thank you for reporting the issue and providing detailed steps to reproduce it.

To help us better understand the problem, could you please try the following workaround? Modify the generated kubeconfig file so that the command:
command: aws is replaced with the absolute path to the AWS CLI

If this resolves the issue, it might be related to your shell environment. Please let us know if this helps or if the problem persists.

Looking forward to your feedback, and thank you for your patience!