WIP: poc: OIDC patch for restrictusers

[everettraven]

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[openshift-ci-robot]

@everettraven: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 276310a|WIP: poc: OIDC patch for restrictusers: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci-robot]

@everettraven: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 276310a|WIP: poc: OIDC patch for restrictusers: does not specify an upstream backport in the commit message
• 7a3a6aa|WIP: poc: OIDC patch for restrictusers: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@everettraven: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 19b0da7|go fmt: does not specify an upstream backport in the commit message
• 276310a|WIP: poc: OIDC patch for restrictusers: does not specify an upstream backport in the commit message
• 7a3a6aa|WIP: poc: OIDC patch for restrictusers: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@everettraven: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 19b0da7|go fmt: does not specify an upstream backport in the commit message
• 276310a|WIP: poc: OIDC patch for restrictusers: does not specify an upstream backport in the commit message
• 7a3a6aa|WIP: poc: OIDC patch for restrictusers: does not specify an upstream backport in the commit message
• 9a06f9d|go fmt: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@everettraven: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 19b0da7|go fmt: does not specify an upstream backport in the commit message
• 276310a|WIP: poc: OIDC patch for restrictusers: does not specify an upstream backport in the commit message
• 2ed95e1|skip oauth-apiserver conection check if authentication mode is OIDC: does not specify an upstream backport in the commit message
• 7a3a6aa|WIP: poc: OIDC patch for restrictusers: does not specify an upstream backport in the commit message
• 9a06f9d|go fmt: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@everettraven: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 19b0da7|go fmt: does not specify an upstream backport in the commit message
• 276310a|WIP: poc: OIDC patch for restrictusers: does not specify an upstream backport in the commit message
• 2ed95e1|skip oauth-apiserver conection check if authentication mode is OIDC: does not specify an upstream backport in the commit message
• 61014ac|better early termination of reachability check: does not specify an upstream backport in the commit message
• 7a3a6aa|WIP: poc: OIDC patch for restrictusers: does not specify an upstream backport in the commit message
• 9a06f9d|go fmt: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: everettraven
Once this PR has been reviewed and has the lgtm label, please assign deads2k for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS

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