Cherry pick of #5513 onto release-1.10

[lneves75]

Backporting #5513 into 1.10

Without this change, for example, kops connections using OIDC to the
cluster will receive this error message:

> cannot build kube client for "$CLUSTER_NAME": No Auth Provider found
> for name "oidc"

kubernetes/client-go#345 suggests importing the package path
`plugin/pkg/client/auth/oidc` from `client-go`, but looking at the code
`plugin/pkg/client/auth` will actually handle loading all known auth
plugins for us.

[lneves75]

/assign @mikesplain

[mikesplain]

/ok-to-test

[chrisz100]

/test pull-kops-e2e-kubernetes-aws

[chrisz100]

/lgtm

[gwohletz]

This appears to have missed the 1.10 release, making it unusable with oidc, please include in the next release

[lneves75]

/assign @mikesplain

[mikesplain]

We're trying to push out 1.11 so I'm not sure if we're doing any patches to 1.10 at the moment. Lets hold off on merging this until we know for sure.

[eyalzek]

Is this on the 1.11 alpha release?

[justinsb]

This will be in 1.11 (you can see the branches in the original PR).

I'm wavering on whether this is a feature or a bugfix, but I'm going to merge it.

Thanks @ripta and @lneves75

/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: justinsb, lneves75

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [justinsb]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[rdrgmnzs]

/test pull-kops-e2e-kubernetes-aws

[justinsb]

The first failure was a double-build of protokube (changed SHA)

[k8s-ci-robot]

@lneves75: The following test failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
pull-kops-e2e-kubernetes-aws	030ee77	link	/test pull-kops-e2e-kubernetes-aws

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[justinsb]

These failures are because I didn't set up the PR test job for 1.10 correctly, but it'll get tested post-merge anyway (every 6 hours). Merging manually!