[release-4.20] Promote BYO OIDC features

[liouk]

This is a manual regeneration and backport of #2454.

Respective approved SBAR: https://docs.google.com/presentation/d/1MrqVU10UYBHNvCu5XrybHejHcqLRf1zsedCYv1hlZVQ/edit?slide=id.g37f5a0492ea_0_0#slide=id.g37f5a0492ea_0_0

[openshift-ci]

Hello @liouk! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign everettraven 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:

• OWNERS

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

[everettraven]

This should not merge until the 4.20 branch is open for z-stream backports.

/hold

[everettraven]

/assign

[liouk]

/test verify-feature-promotion

[liouk]

/test verify-feature-promotion

[liouk]

/test verify-feature-promotion

[xingxingxia]

/retest-required

[xingxingxia]

Though there were still some Required jobs failing, I anyway pre-merge tested this PR + openshift/cluster-authentication-operator#802 together with

# Payload 1
build 4.20.0-0.nightly-2025-10-21-003434,openshift/api#2515,openshift/cluster-authentication-operator#802

# Payload 2
build 4.20.0-0.nightly-2025-10-21-173356,openshift/api#2515,openshift/cluster-authentication-operator#802

In a fresh env of cluster-bot payload 1, configured external oidc with Entra ID, pre-upgrade related tests passed including oc / console interactive logins, extra / uid checks, clusterversion/version and authentication.config/cluster and co/authentication's .status against their respecitve Jira bugs et al.
Upgrading of the env to cluster-bot payload 2 succeeded without the filed upgrade bug any more. Post-upgrade tests passed.
Regression tests of rollback to IDP and post-rollback interactive logins also passed.

So adding /verified label:
/verified by @xingxingxia

I didn't yet have chance to cover testing 4.19 -> upgrade to 4.20-external-oidc-GA-clusterbot-payload -> configure external oidc, also didn't test 4.20.0 -> upgrade to 4.20-external-oidc-GA-clusterbot-payload -> configure external oidc. Because I had tested "4.21-nightly-payload -> upgrade to 4.21-external-oidc-GA-clusterbot-payload -> configure external oidc" without issue, I believe same confidence.

[openshift-ci-robot]

@xingxingxia: This PR has been marked as verified by @xingxingxia.

In response to this:

Though there were still some Required jobs failing, I anyway pre-merge tested this PR + openshift/cluster-authentication-operator#802 together with

# Payload 1
build 4.20.0-0.nightly-2025-10-21-003434,openshift/api#2515,openshift/cluster-authentication-operator#802

# Payload 2
build 4.20.0-0.nightly-2025-10-21-173356,openshift/api#2515,openshift/cluster-authentication-operator#802

In a fresh env of cluster-bot payload 1, configured external oidc with Entra ID, pre-upgrade related tests passed including oc / console interactive logins, extra / uid checks, clusterversion/version and authentication.config/cluster and co/authentication's .status against their respecitve Jira bugs et al.
Upgrading of the env to cluster-bot payload 2 succeeded without the filed upgrade bug any more. Post-upgrade tests passed.
Regression tests of rollback to IDP and post-rollback interactive logins also passed.

So adding /verified label:
/verified by @xingxingxia

I didn't yet have chance to cover testing 4.19 -> upgrade to 4.20-external-oidc-GA-clusterbot-payload -> configure external oidc, also didn't test 4.20.0 -> upgrade to 4.20-external-oidc-GA-clusterbot-payload -> configure external oidc. Because I had tested "4.21-nightly-payload -> upgrade to 4.21-external-oidc-GA-clusterbot-payload -> configure external oidc" without issue, I believe same confidence.

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 openshift-eng/jira-lifecycle-plugin repository.

[liouk]

/test verify-feature-promotion

[openshift-ci]

@liouk: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-ovn-hypershift	88a5beb	link	true	/test e2e-aws-ovn-hypershift
ci/prow/verify-feature-promotion	88a5beb	link	true	/test verify-feature-promotion

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.