OIDC authentication seems broken in 2.3.0

[desaintmartin]

After downloading the latest version 2.3.0, OIDC-based authentication no longer works.

- name:xxx
  user:
    auth-provider:
      config:
        client-id: xxx
        client-secret: xxx
        id-token: xxx
        idp-issuer-url: https://xxx.com
        refresh-token: XXX
      name: oidc

[i-sam]

also doesn't work authentication to EKS with aws-iam-authenticator

[dkapanidis]

For authentication to EKS with aws-iam-authenticator try to update the binary path to absolute one, kubernetic may not have the same PATH variable as your shell to lookup the binary.

tell me if that works, so I can check in more detail if it doesn't.

For OIDC authentication this is a regression, due to switch of the node kubernetes client to the official one, which didn't support it yet. kubernetes-client/javascript#303 probably fixes it.

[machine424]

@dkapanidis , The official JS kubernetes client doesn't support (yet) persisting oidc tokens in the configfile after refreshing them (kubernetes-client/javascript#340), does Kubernetic deal with that on its own ? We use many clients (kubectl, python client and Kubernetic) at the same time, but sometimes a client may end up loading old tokens from the configfile and we're forced to do the refresh manually. Thanks

[dkapanidis]

Kubernetic has switched from JS client to Go client for kubernetes connectivity recently, so this should no longer be an issue.

For aws-iam-authenticator external binary, bare in mind that the cli PATH env variable is not propagated to the App, there is a Preferences section where you can define extra PATH variables which contain external binaries: