-
Notifications
You must be signed in to change notification settings - Fork 106
Pull requests: openshift/sriov-network-operator
Author
Label
Projects
Milestones
Reviews
Assignee
Sort
Pull requests list
Merge https://github.com/k8snetworkplumbingwg/sriov-network-operator:master into master
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
#1010
opened Oct 2, 2024 by
SchSeba
Loading…
[release-4.12] OCPBUGS-42507: update owners
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.
#1009
opened Sep 26, 2024 by
openshift-cherrypick-robot
Loading…
OCPBUGS-42252: [release-4.17] Preserve user defined annotations on 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/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.
SriovNetworks
approved
#1008
opened Sep 20, 2024 by
zeeke
Loading…
OCPBUGS-41183: Updating sriov-network-config-daemon-container image to be consistent with ART for 4.18
backport-risk-assessed
Indicates a PR to a release branch has been evaluated and considered safe to accept.
bugzilla/valid-bug
Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting.
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.
#1002
opened Sep 5, 2024 by
openshift-bot
Loading…
OCPBUGS-37668: [release-4.17]: Fix operator quick restart for SNO
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
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.
#1001
opened Sep 4, 2024 by
zeeke
Loading…
OCPBUGS-39512: Updating sriov-network-webhook-container image to be consistent with ART for 4.18
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.
bugzilla/valid-bug
Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting.
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.
#1000
opened Sep 4, 2024 by
openshift-bot
Loading…
OCPBUGS-39355: release[4.16] allow to remove a sriovPool named default
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/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.
#994
opened Sep 2, 2024 by
SchSeba
Loading…
OCPBUGS-22908: Match origin image to configured image reference
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/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
#859
opened Nov 1, 2023 by
ashwindasr
Loading…
ProTip!
Follow long discussions with comments:>50.