-
Notifications
You must be signed in to change notification settings - Fork 244
Issues: openshift/cluster-network-operator
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
[release-4.19] OCPBUGS-55645: Remove environment variables related to ARO HCP MIv2 for CNO
jira/invalid-bug
Indicates that a referenced Jira bug is invalid for the branch this PR is targeting.
jira/severity-low
Referenced Jira bug's severity is low for the branch this PR is targeting.
jira/valid-reference
Indicates that this PR references a valid Jira ticket of any type.
#2701
opened May 7, 2025 by
openshift-cherrypick-robot
Loading…
[release-4.18] OCPBUGS-55011: Add missing backendAddressPools read permission on azure
jira/invalid-bug
Indicates that a referenced Jira bug is invalid for the branch this PR is targeting.
jira/severity-critical
Referenced Jira bug's severity is critical for the branch this PR is targeting.
jira/valid-reference
Indicates that this PR references a valid Jira ticket of any type.
#2688
opened Apr 15, 2025 by
openshift-cherrypick-robot
Loading…
[release-4.17] OCPBUGS-45086: Re-disable metrics server
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.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
qe-approved
Signifies that QE has signed off on this PR
#2579
opened Nov 26, 2024 by
openshift-cherrypick-robot
Loading…
[release-4.17] OCPBUGS-44187: fix annotation from deployment to pod
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/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.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
#2555
opened Nov 4, 2024 by
openshift-cherrypick-robot
Loading…
ProTip!
Mix and match filters to narrow down what you’re looking for.