Skip to content

Pull requests: openshift/kubernetes

New pull request New
14 Open 1,877 Closed
14 Open 1,877 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

MULTIARCH-4229: UPSTREAM:<carry>:bump cadvisor for 3516 upstream patches 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. kind/feature Categorizes issue or PR as related to a new feature. vendor-update Touching vendor dir or related files
#2012 opened Jul 4, 2024 by harche Loading…
5
[WIP] k8s 1.31 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. vendor-update Touching vendor dir or related files
#2004 opened Jul 1, 2024 by soltysh • Draft
8
[WIP] Fix httplog not logging watch duration in separate goroutines 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. vendor-update Touching vendor dir or related files
#1999 opened Jun 26, 2024 by dinhxuanvu Loading…
3
[WIP] Disable APIServingWithRoutine featuregate by default 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. vendor-update Touching vendor dir or related files
#1997 opened Jun 25, 2024 by dinhxuanvu Loading…
3
[release-4.15] OCPBUGS-35331: UPSTREAM: 124795: e2e: DaemonSet maxSurge test should account for terminated pods 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. 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.
#1988 opened Jun 12, 2024 by openshift-cherrypick-robot Loading…
@soltysh @atiratree
@kasturinarra @zhouying7780 @xingxingxia @sunilcio @duanwei33 @wangke19 @gangwgr
7
test commit for OCPBUGS-33783 backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs.
#1971 opened May 16, 2024 by harche Loading…
17
OCPBUGS-31467: Return from EnsureHostInPool on all NIC errors backports/unvalidated-commits Indicates that not 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. lgtm Indicates that a PR is ready to be merged. vendor-update Touching vendor dir or related files
#1964 opened May 7, 2024 by nrb Loading…
@JoelSpeed
6
NO REVIEW NEEDED: this is a placeholder PR for debugging backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. vendor-update Touching vendor dir or related files
#1960 opened May 2, 2024 by machine424 Loading…
12
PROOF replace github.com/openshift/api->github.com/sanchezl/api@deploymentconfig backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. vendor-update Touching vendor dir or related files
#1921 opened Mar 28, 2024 by sanchezl Loading…
6
WIP: use the right feature gate when reconstructing volumes 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. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
#1918 opened Mar 25, 2024 by bertinatto Loading…
4
[release-4.15] OCPBUGS-30731: Upstream: <carry>: RPM: Split apiserver, scheduler, k-c-m, kubelet into subpackages 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. 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.
#1906 opened Mar 11, 2024 by openshift-cherrypick-robot Loading…
@sdodson
8
add logs when root container does not exist 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. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
#1896 opened Feb 22, 2024 by harche • Draft
8
[release-4.14] UPSTREAM: 120961: e2e: bootstrap vsphere tests earlier 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. backports/validated-commits Indicates that all commits come to merged upstream PRs. 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.
#1730 opened Oct 2, 2023 by mkowalski Loading…
@bertinatto @kasturinarra
@zhouying7780 @xingxingxia @sunilcio @duanwei33 @wangke19 @gangwgr
33
DO NOT MERGE: ocp-next 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. 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. vendor-update Touching vendor dir or related files
#1647 opened Jul 27, 2023 by bertinatto • Draft
170
ProTip! Filter pull requests by the default branch with base:master.