Cluster not Reachable when exec Authentication is used

[hofq]

Bug description

For Authentication on Prod we use azure/kubelogin. It seems like it is not compatible to Podman Desktop

Operating system

macos sonoma 14

Installation Method

Brew (macOS)

Version

1.8.0

Steps to reproduce

• Open Podman Desktop
• Select AWS Cluster, authenticated with kubelogin from azure or with aws-iam-authenticator
• Receive Error below

Relevant log output

No response

Additional context

User Authentication snippet Kubelogin:

user:
- name: azure-user-roc-kubelogin
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1beta1
      args:
      - get-token
      - "--environment"
      - AzurePublicCloud
      - "--server-id"
      - <client id>
      - "--client-id"
      - <client id>
      - "--tenant-id"
      - <tenant id>
      command: kubelogin
      env: null
      interactiveMode: IfAvailable
      provideClusterInfo: false

Used Package for auth:
https://github.com/Azure/kubelogin

User Authentication snippet Kubelogin:

- name: user-1.eksctl.io
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1beta1
      args:
      - token
      - "-i"
      - roc-prod
      command: aws-iam-authenticator
      env:
      - name: AWS_STS_REGIONAL_ENDPOINTS
        value: regional
      - name: AWS_DEFAULT_REGION
        value: eu-central-1
      interactiveMode: IfAvailable
      provideClusterInfo: false

[kwkelly]

I get the same error using exec authentication with aws.

I suspect this has to do with the availability (or lack thereof) of the command for the exec in the path.

I have the aws command installed at /usr/local/bin/aws, and if I start podman desktop and omit /usr/local/bin from the PATH (e.g. PATH=/usr/bin open /Applications/Podman\ Desktop.app/), I get the TypeError: Cannot read properties of null (reading 'toString')) error.

On the other hand, if I make sure that authentication command is available in my path (e.g. PATH=/usr/local/bin:/usr/bin open /Applications/Podman\ Desktop.app/), it works just fine.

So in your kube config file, you can add the path where the command is installed as part of the env config.

env:
   - name: PATH
     value: $PATH:/usr/local/bin

you'll have to do this for each user/context. You could also add the command to one of your global paths (on macos those that are in /etc/paths)