Skip to content

Pull requests: openshift/microshift

New pull request New
11 Open 4,451 Closed
11 Open 4,451 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

USHIFT-5568: Split AI Model Serving manifest 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.
#4782 opened Apr 9, 2025 by pmtk Loading…
4
NO-ISSUE: rebase-main-4.19.0-0.nightly-2025-04-08-163320_amd64-2025-04-08_arm64-2025-04-08 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. 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. lgtm Indicates that a PR is ready to be merged. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.
#4781 opened Apr 9, 2025 by microshift-rebase-script bot Loading…
@pmtk
6
USHIFT-5561: Introduce e2e scenarios for telemetry approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#4780 opened Apr 8, 2025 by pacevedom Loading…
4
USHIFT-5529: Move bootc layer2-presubmit/group3 to periodics jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#4777 opened Apr 7, 2025 by vanhalenar Loading…
6
USHIFT-2575: add 2 telemetry test cases approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#4769 opened Apr 4, 2025 by agullon Loading…
4
USHIFT-5518: Add telemetry proxy settings and tests 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.
#4768 opened Apr 4, 2025 by pacevedom Loading…
@agullon
21
USHIFT-5400 add observability profiles approved Indicates a PR has been approved by an approver from all required OWNERS files.
#4757 opened Apr 3, 2025 by copejon Loading…
7
USHIFT-5477: Split MicroShift Image Mode docs into user and contributor parts 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.
#4753 opened Apr 1, 2025 by ggiguash Loading…
@DanielFroehlich
44
Add Fault Tests approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command.
#4743 opened Mar 28, 2025 by agullon Loading…
7
USHIFT-5531: Auto-rebase procedure with flannel and kube-proxy image update jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#4726 opened Mar 24, 2025 by praveenkumar Loading…
13
[release-4.15] OCPBUGS-54714: Upgrade openvswitch package version to 3.3 approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/invalid-bug Indicates that a referenced Jira bug is invalid 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.
#4700 opened Mar 18, 2025 by igsilya Loading…
@ggiguash
24
ProTip! Follow long discussions with comments:>50.