Skip to content

Pull requests: openshift/oauth-apiserver

New pull request New
10 Open 150 Closed
10 Open 150 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Reviews
Filter by reviews
No reviews Review required Approved review Changes requested
Assignee
Filter by who’s assigned
Assigned to nobody Loading
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Pull requests list

[WIP]CNTRLPLANE-2260:test/e2e: migrate tokenreviews test to OTE framework do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#163 opened Dec 23, 2025 by wangke19 Loading…
4
CNTRLPLANE-2260:cmd/oauth-apiserver-tests-ext: Update OTE framework integration approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria
#162 opened Dec 23, 2025 by wangke19 Loading…
@p0lyn0mial
12
OCPBUGS-65926: chore: sync with o/kubernetes-apiserver openshift-apiserver-4.20-kubernetes-1.33 do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#159 opened Dec 3, 2025 by ingvagabund Loading…
4
Update OWNERS files
#158 opened Dec 2, 2025 by wangke19 Loading…
3
OCPBUGS-66228: UPSTREAM <carry>: bump kubernetes-apiserver to pick up loopback certificate expiration update jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#157 opened Dec 1, 2025 by dinhxuanvu Loading…
4
Migrate away from deprecated ioutil
#156 opened Nov 24, 2025 by sebrandon1 Loading…
2
feat: add readyz for user informer sync do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.
#153 opened Nov 19, 2025 by ricardomaraschini • Draft
5
test revert lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#145 opened Sep 15, 2025 by xueqzhan Loading…
11
OCPBUGS-57611: Updating ose-oauth-apiserver-container image to be consistent with ART for 4.20 backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#134 opened Jun 18, 2025 by openshift-bot Loading…
@benluddy
12
OCPBUGS-45435: Updating ose-oauth-apiserver-container image to be consistent with ART for 4.19 backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
#125 opened Dec 4, 2024 by openshift-bot Loading…
@sanchezl
20
ProTip! Updated in the last three days: updated:>2025-12-21.