-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Pull requests: cri-o/cri-o
Author
Label
Projects
Milestones
Reviews
Assignee
Sort
Pull requests list
perf(memorystore): optimize Size() to O(1)
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
needs-ok-to-test
Indicates a PR that requires an org member to verify it is safe to test.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
#9680
opened Dec 22, 2025 by
ankit98040
Loading…
build(deps): bump the gomod group across 1 directory with 3 updates
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
release-note-none
Denotes a PR that doesn't merit a release note.
#9679
opened Dec 18, 2025 by
dependabot
bot
Loading…
📝 Add docstrings to Indicates the PR's author has not DCO signed all their commits.
do-not-merge/release-note-label-needed
Indicates that a PR should not merge because it's missing one of the release note labels.
needs-ok-to-test
Indicates a PR that requires an org member to verify it is safe to test.
terminating-pod
dco-signoff: no
#9678
opened Dec 18, 2025 by
coderabbitai
bot
Loading…
Use cgroups.CgroupStats for stats collection
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
release-note-none
Denotes a PR that doesn't merit a release note.
#9676
opened Dec 18, 2025 by
bitoku
Loading…
OCPBUGS-69670: [release-1.33] : Ensure InitLabel only sets process label when unset
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
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.
lgtm
Indicates that a PR is ready to be merged.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
#9674
opened Dec 17, 2025 by
openshift-cherrypick-robot
Loading…
rebuild
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
do-not-merge/release-note-label-needed
Indicates that a PR should not merge because it's missing one of the release note labels.
#9669
opened Dec 16, 2025 by
haircommander
Loading…
Refactor mount and selinux codes in container creation.
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
release-note-none
Denotes a PR that doesn't merit a release note.
#9667
opened Dec 16, 2025 by
bitoku
Loading…
OCPBUGS-62150: [release-1.31] server: ignore /etc/passwd mount
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
jira/invalid-bug
Indicates that a referenced Jira bug is invalid for the branch this PR is targeting.
jira/severity-moderate
Referenced Jira bug's severity is moderate for the branch this PR is targeting.
jira/valid-reference
Indicates that this PR references a valid Jira ticket of any type.
kind/bug
Categorizes issue or PR as related to a bug.
release-note-none
Denotes a PR that doesn't merit a release note.
#9662
opened Dec 15, 2025 by
adrianreber
Loading…
WIP: [1.32] container: filter thermal_throttle masked paths
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
release-note-none
Denotes a PR that doesn't merit a release note.
#9661
opened Dec 15, 2025 by
saschagrunert
Loading…
Follow up on PR #9634 to clean up redundant code
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
lgtm
Indicates that a PR is ready to be merged.
ok-to-test
Indicates a non-member PR verified by an org member that is safe to test.
release-note-none
Denotes a PR that doesn't merit a release note.
#9660
opened Dec 13, 2025 by
HirazawaUi
Loading…
Add image content cache to retain compressed layers for P2P distribution
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
kind/feature
Categorizes issue or PR as related to a new feature.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
#9628
opened Dec 1, 2025 by
sohankunkerkar
Loading…
Rename CPU load balancing tests and add test for cgroup v2
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
kind/other
Categorizes issue or PR as not clearly related to any existing kind/* category
release-note-none
Denotes a PR that doesn't merit a release note.
#9622
opened Nov 28, 2025 by
bitoku
Loading…
[release-1.31] c/image test patch-4-18
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
do-not-merge/release-note-label-needed
Indicates that a PR should not merge because it's missing one of the release note labels.
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
[release-1.27] OCPBUGS-55964: Pause container during checkpointing
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
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.
kind/bug
Categorizes issue or PR as related to a bug.
release-note-none
Denotes a PR that doesn't merit a release note.
#9616
opened Nov 24, 2025 by
adrianreber
Loading…
feat: allow exec to containers during graceful termination
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
ok-to-test
Indicates a non-member PR verified by an org member that is safe to test.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
#9614
opened Nov 21, 2025 by
willianpaixao
Loading…
highperformancehooks: fix some ordering issues with irq smp affinity
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
kind/bug
Categorizes issue or PR as related to a bug.
lgtm
Indicates that a PR is ready to be merged.
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
#9613
opened Nov 20, 2025 by
haircommander
Loading…
feat: add reverse port forwarding support via pod annotations
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
do-not-merge/release-note-label-needed
Indicates that a PR should not merge because it's missing one of the release note labels.
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
needs-ok-to-test
Indicates a PR that requires an org member to verify it is safe to test.
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#9612
opened Nov 20, 2025 by
willianpaixao
•
Draft
6 tasks done
wip: test ci
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
do-not-merge/release-note-label-needed
Indicates that a PR should not merge because it's missing one of the release note labels.
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.
#9572
opened Nov 5, 2025 by
haircommander
Loading…
Replace json-iterator/go with goccy/go-json
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
kind/dependency-change
Categorizes issue or PR as related to changing dependencies
release-note-none
Denotes a PR that doesn't merit a release note.
#9566
opened Nov 3, 2025 by
sohankunkerkar
Loading…
Update nixpkgs
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
kind/ci
Categorizes issue or PR as related to CI
ok-to-test
Indicates a non-member PR verified by an org member that is safe to test.
release-note-none
Denotes a PR that doesn't merit a release note.
#9542
opened Nov 1, 2025 by
github-actions
bot
Loading…
[release-1.31] Multiple patches to fix OCPBUGS-63432
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
release-note-none
Denotes a PR that doesn't merit a release note.
#9530
opened Oct 23, 2025 by
openshift-cherrypick-robot
Loading…
[release-1.33] OCPBUGS-59321: HighPerformanceHooks: Atomic locking and fix container replacement race conditions
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
jira/invalid-bug
Indicates that a referenced Jira bug is invalid for the branch this PR is targeting.
jira/severity-moderate
Referenced Jira bug's severity is moderate for the branch this PR is targeting.
jira/valid-reference
Indicates that this PR references a valid Jira ticket of any type.
release-note-none
Denotes a PR that doesn't merit a release note.
#9491
opened Oct 2, 2025 by
openshift-cherrypick-robot
Loading…
[WIP] *: add goroutine monitoring
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
kind/feature
Categorizes issue or PR as related to a new feature.
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.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
#9477
opened Sep 23, 2025 by
sohankunkerkar
•
Draft
fix: create container log directories to prevent conmon failures
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
kind/feature
Categorizes issue or PR as related to a new feature.
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
ok-to-test
Indicates a non-member PR verified by an org member that is safe to test.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
#9470
opened Sep 19, 2025 by
T0MASD
Loading…
include workload allowed_annotations in crio config output
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
kind/bug
Categorizes issue or PR as related to a bug.
ok-to-test
Indicates a non-member PR verified by an org member that is safe to test.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
#9468
opened Sep 17, 2025 by
prasad89
Loading…
Previous Next
ProTip!
Updated in the last three days: updated:>2025-12-19.