Skip to content

Pull requests: openshift/openshift-apiserver

New pull request New
15 Open 566 Closed
15 Open 566 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

OCPBUGS-70049: Updating ose-openshift-apiserver-container image to be consistent with ART for 4.22 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. verified Signifies that the PR passed pre-merge verification criteria
#590 opened Dec 20, 2025 by openshift-bot Loading…
@dgrisonnet
6
[release-4.18] OCPBUGS-69955: Add ValidatingAdmissionPolicy and check for omissions next time. approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#589 opened Dec 19, 2025 by openshift-cherrypick-robot Loading…
@benluddy @xingxingxia
@wangke19 @gangwgr
6
[release-4.18] OCPBUGS-66379: pkg/image: conditionally parse raw image manifest approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. 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. lgtm Indicates that a PR is ready to be merged.
#585 opened Dec 4, 2025 by openshift-cherrypick-robot Loading…
@ricardomaraschini
10
OCPBUGS-66229: 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/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#584 opened Dec 1, 2025 by dinhxuanvu Loading…
4
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.
#580 opened Nov 24, 2025 by ingvagabund Loading…
6
[WIP] Implement runAsGroup validation check do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.
#574 opened Nov 12, 2025 by ropatil010 Loading…
3
[WIP]Refactor test/extended to use OpenShift Tests Extension (OTE) framework do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#568 opened Oct 23, 2025 by wangke19 Loading…
17
[WIP]Create separate Go module for OTE test extension and migrating OCP-25806 to component repo do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#563 opened Oct 16, 2025 by gangwgr Loading…
23
route: Update OWNERS lgtm Indicates that a PR is ready to be merged.
#558 opened Sep 17, 2025 by alebedev87 Loading…
@Miciah
7
NO-JIRA: Update README.md with diagram 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. 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.
#541 opened Aug 25, 2025 by wangke19 Loading…
@sanchezl @gangwgr
12
proto: don't skip synchronize on deletes approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
#534 opened Aug 14, 2025 by sanchezl • Draft
9
WIP: WRKLDS-1599: Update to distribution/[email protected] 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. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#532 opened Jul 9, 2025 by tchap Loading…
11
WIP: OCPBUGS-57474: Authorization Cache V2 do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. 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. 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.
#530 opened Jun 24, 2025 by jacobsee • Draft
28
OCPBUGS-38120: Improve error messages for project Delete errors 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/stale Denotes an issue or PR has remained open with no activity and has become stale.
#520 opened May 28, 2025 by vrutkovs Loading…
48
DO-NOT-MERGE: Proof PR for library-go#1964 do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. 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.
#512 opened May 21, 2025 by liouk Loading…
7
ProTip! Exclude everything labeled bug with -label:bug.