Fix OIDC authentication support

[jpiper]

What type of PR is this?
/kind bug

What this PR does / why we need it:

The imports the k8s OIDC libraries so that OIDC authentication to the kubernetes apiserver works. At the moment, if you are trying to run ingress2gateway against a kubernetes cluster that is configured in your kubeconfig to use OIDC, you get the following error

$ ./ingress2gateway print --providers ingress-nginx
Error: failed to create client: no Auth Provider found for name "oidc"
...

Once the OIDC auth libraries are imported this now works fine

$ ./ingress2gateway print --providers ingress-nginx -n piperj
No resources found in piperj namespace

This should also fix GCP and Azure logins as well as those auth libraries are part of this fix as well.

Which issue(s) this PR fixes:

Fixes #215

Does this PR introduce a user-facing change?:

Fix invocations for OIDC-enabled clusters from kubeconfig

[k8s-ci-robot]

Welcome @jpiper!

It looks like this is your first PR to kubernetes-sigs/ingress2gateway 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/ingress2gateway has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @jpiper. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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-sigs/prow repository.

[rikatz]

/ok-to-test
@jpiper can you just provide an example of how this failed, just to be clear on the PR description? eg.: where you on a cloud provider, you did logged in and by some reason something failed?

Thanks!

[jpiper]

Hi @rikatz I've added some more detail to the PR and fixed the build! Thanks

[rikatz]

/lgtm
Thanks!

/cc @LiorLieberman

[LiorLieberman]

Sweet, thank you @jpiper!

/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jpiper, LiorLieberman

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [LiorLieberman]

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