Unable to connect to Azure Kubernetes Cluster - devicelogin is not supported if interactiveMode is 'never'

[mgvinuesa]

Describe the bug
It is not possible to connect from Lens to Azure Kubernetes Cluster

To Reproduce
From command line it is possible to do with the following commands

az login --use-device
az account set --subscription
az aks get-credentials --resource-group --name
kubectl ...

Expected behavior
Interact with the cluster

Screenshots

Environment (please complete the following information):

• Lens Version:
  

• OS: [e.g. OSX] Windows 12

• Installation method (e.g. snap or AppImage in Linux):

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

info: [CLUSTER]: refresh {"accessible":false,"disconnected":false,"id":"3bf40ecd91d16eaaf6ddb05088190c3a","name":"<name>","online":false,"ready":false}
error: [CLUSTER]: Failed to connect to "<name>": StatusCodeError: 500 - "getting credentials: exec: executable kubelogin failed with exit code 1\n"```

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: <DATA>
    server: <URL>
  name: <CLUSTER NAME>
contexts:
- context:
    cluster: <CLUSTER NAME>
    user: <CLUSTER USER>
  name: <CLUSTER NAME>
current-context: <CLUSTER NAME>
kind: Config
preferences: {}
users:
- name: <CLUSTER USER>
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1beta1
      args:
      - get-token
      - --environment
      - AzurePublicCloud
      - --server-id
      - <SERVER ID>
      - --client-id
      - <CLIENT ID>
      - --tenant-id
      - <TENANT ID>
      - --login
      - devicecode
      command: kubelogin
      env: null
      provideClusterInfo: false

Additional context
Add any other context about the problem here.

[olefritsch]

Same here after updating Lens to version 6.1.19

[anderslaub]

I am experiencing the same too - just updated to Lens v6.1.19 and now cannot connect to any clusters (all on AKS).

No issue connecting with kubectl / k9s and no changes made to kubeconfig since long before upgrade where everything worked smooth.

[stefan-oconnell]

I'm on 6.0.2 but having the same issue trying to log into an AKS with device login for the first time on this install.

[stefan-oconnell]

For anyone else having this issue, I had kubelogin v0.21, tried updating to v0.22 no dice. Co-working with v0.20 had no issues, so I downgraded and it works again.

Some interaction with lens and that kubelogin version is busted, use v0.20 if possible: https://github.com/Azure/kubelogin/releases/tag/v0.0.20

[ayelencasamassa]

Hey, same issue here but connecting AzDo with private AKS.
The solution for me was this:

task: AzureCLI@2
inputs:
azureSubscription: 'ARM MANUAL SERVICE CONNECTION'
scriptType: 'bash'
scriptLocation: 'inlineScript'
inlineScript: |
az aks get-credentials -n CLUSTERNAME -g CLUSTERRESOURCEGROUP
kubelogin convert-kubeconfig -l azurecli
kubectl get nodes

I took the example from here: https://blog.baeke.info/2021/06/03/a-quick-look-at-azure-kubelogin/

I'm using kubelogin v0.22 and AKS 1.24.6

[ColinBe95]

For me this was resolved by updating my kubeconfig using:
kubelogin convert-kubeconfig -l azurecli

[hungtran84]

@mgvinuesa I faced the same issue and below is what I've done to fix it:

1. Remove the installed kubelogin

brew uninstall kubelogin

2. Install Azure kubelogin

kubelogin convert-kubeconfig

3. Convert the existing kubeconfig

kubelogin convert-kubeconfig

Hope this helps

[christopherdufort]

Was able to resolve this in windows by bumping kubelogin to v0.0.24+
https://github.com/Azure/kubelogin/releases/tag/v0.0.24

as they rolled back the device login commits:
Azure/kubelogin#155
Azure/kubelogin#150