Skip to content

Pull requests: openshift/kubernetes

New pull request New
36 Open 2,053 Closed
36 Open 2,053 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
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Pull requests list

OCPBUGS-49906: Bump k8s api to 1.29.14 approved Indicates a PR has been approved by an approver from all required OWNERS files. backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. 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. vendor-update Touching vendor dir or related files
#2211 opened Feb 18, 2025 by jerpeter1 Loading…
3
OCPBUGS-51006: Bump k8s api to 1.30.10 approved Indicates a PR has been approved by an approver from all required OWNERS files. backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. 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. vendor-update Touching vendor dir or related files
#2210 opened Feb 18, 2025 by jerpeter1 Loading…
3
CNTRLPLANE-1: Bump 1.32.2 backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. vendor-update Touching vendor dir or related files
#2209 opened Feb 17, 2025 by dusk125 Loading…
@bertinatto
12
OCPBUGS-50929: Update to Kubernetes v1.31.6 backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. 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. vendor-update Touching vendor dir or related files
#2208 opened Feb 17, 2025 by atiratree Loading…
@bertinatto
4
OCPBUGS-50881: kubelet: fix a stall on startup from waiting too long for a stat call backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. lgtm Indicates that a PR is ready to be merged. vendor-update Touching vendor dir or related files
#2206 opened Feb 12, 2025 by haircommander Loading…
@harche
7
wip: release-4.18: staticpod block adding revisioned operand backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.
#2205 opened Feb 12, 2025 by benluddy Loading…
6
[release-4.17] OCPBUGS-50564: UPSTREAM: 129180: prevent unnecessary resolving of iscsi/fc devices to dm approved Indicates a PR has been approved by an approver from all required OWNERS files. backports/validated-commits Indicates that all commits come to merged upstream PRs. 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. lgtm Indicates that a PR is ready to be merged.
#2203 opened Feb 11, 2025 by openshift-cherrypick-robot Loading…
@bertinatto @RomanBednar
11
UPSTREAM: <carry>: add minimumkubeletversion admission package backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. vendor-update Touching vendor dir or related files
#2201 opened Feb 7, 2025 by haircommander Loading…
31
OCPBUGS-45359: Bump CSI sidecars to fix resizing tests backports/validated-commits Indicates that all commits come to merged upstream PRs. 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.
#2196 opened Feb 3, 2025 by gnufied Loading…
13
Revert "disable ResilientWatchCacheInitialization feature" backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. vendor-update Touching vendor dir or related files
#2192 opened Jan 30, 2025 by benluddy Loading…
4
DO NOT MERGE: Test PodRejectionStatus backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs.
#2189 opened Jan 29, 2025 by bitoku Loading…
12
TRT-1836: UPSTREAM: <carry>: remove old k8s-tests external binary backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#2178 opened Jan 20, 2025 by stbenjam Loading…
4
DO NOT MERGE: With stack approved Indicates a PR has been approved by an approver from all required OWNERS files. backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. vendor-update Touching vendor dir or related files
#2173 opened Jan 15, 2025 by deads2k Loading…
3
DO NOT MERGE: add instrumenting to chase very short watches approved Indicates a PR has been approved by an approver from all required OWNERS files. backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. vendor-update Touching vendor dir or related files
#2172 opened Jan 15, 2025 by deads2k Loading…
4
UPSTREAM: <carry>: add audit annotations to track etcd state acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. vendor-update Touching vendor dir or related files
#2170 opened Jan 13, 2025 by deads2k Loading…
@benluddy
7
TEST: null-hypothesis approved Indicates a PR has been approved by an approver from all required OWNERS files. backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. 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.
#2166 opened Dec 18, 2024 by jerpeter1 • Draft
6
[release-4.16] WIP: NOMERGE: DNM: consume u/s LLC alignment support backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs.
#2159 opened Dec 10, 2024 by ffromani Loading…
3
CNTRLPLANE-78: Move Group informer configuration to RestrictSubjectBindings plugin initialization backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#2157 opened Dec 9, 2024 by everettraven Loading…
43
DO NOT MERGE: ocp-next approved Indicates a PR has been approved by an approver from all required OWNERS files. backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. 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. vendor-update Touching vendor dir or related files
#2156 opened Dec 6, 2024 by bertinatto • Draft
25
OCPBUGS-45214: STOR-2285: Add groupsnapshot tests backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. 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.
#2155 opened Dec 6, 2024 by jsafrane Loading…
39
DO NOT MERGE: ocp-next approved Indicates a PR has been approved by an approver from all required OWNERS files. backports/validated-commits Indicates that all commits come to merged upstream PRs. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. vendor-update Touching vendor dir or related files
#2148 opened Nov 28, 2024 by bertinatto • Draft
54
OCPBUGS-37706: allow TLS1.3 or modern profile to be specified backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. jira/severity-important Referenced Jira bug's severity is important 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. qe-approved Signifies that QE has signed off on this PR
#2135 opened Nov 15, 2024 by sanchezl Loading…
@wangke19
22
[release-4.16] WIP: NOMERGE: DNM: consume u/s LLC alignment support backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
#2128 opened Nov 6, 2024 by ffromani Loading…
5
NO-JIRA: UPSTREAM: Add several request/response headers in audit log entries acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. 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. vendor-update Touching vendor dir or related files
#2121 opened Oct 22, 2024 by vrutkovs Loading…
@Elbehery
73
NO-JIRA: UPSTREAM: fix request Host storing in openshift.io/during-graceful audit log annotation acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. backports/validated-commits Indicates that all commits come to merged upstream PRs. 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. vendor-update Touching vendor dir or related files
#2119 opened Oct 22, 2024 by vrutkovs Loading…
@bertinatto
30
ProTip! Mix and match filters to narrow down what you’re looking for.