[Release-1.30] - The "Standalone"-mode of oidc-login in the wrapped kubectl library fails, with: no Auth Provider found for name "oidc"

[brandond]

Backport fix for The "Standalone"-mode of oidc-login in the wrapped kubectl library fails, with: no Auth Provider found for name "oidc"

• The "Standalone"-mode of oidc-login in the wrapped kubectl library fails, with: no Auth Provider found for name "oidc" #11268

[mdrahman-suse]

Validated on RC v1.30.7-rc1+k3s1

Testing

Follow steps: #11273 (comment)

Replication:

$ k3s -v
k3s version v1.30.6+k3s1 (1829eaae)
go version go1.22.8

## Update kubeconfig
$ sudo vi /etc/rancher/k3s/k3s.yaml

$ kubectl auth whoami
error: no Auth Provider found for name "oidc"

Validation:

$ k3s -v
k3s version v1.30.7-rc1+k3s1 (c79db1bd)
go version go1.22.8

## Update kubeconfig
$ sudo vi /etc/rancher/k3s/k3s.yaml

$ kubectl auth whoami
Unable to connect to the server: No valid id-token, and cannot refresh without refresh-token