Skip to content

Pull requests: openshift/cluster-version-operator

New pull request New
21 Open 1,229 Closed
21 Open 1,229 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
Assigned to nobody Loading
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Pull requests list

Set OKD as default featureset for OKD clusters
#1287 opened Jan 6, 2026 by Prashanth684 Loading…
4
OTA-1546: Reconcile cv.spec.desiredUpdate.acceptRisks 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.
#1284 opened Jan 2, 2026 by hongkailiu Loading…
19
[WIP] Allow inclusion/exclusion of manifests based on the OCP major version do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.
#1282 opened Dec 24, 2025 by JoelSpeed • Draft
3
More robust promql inject
#1280 opened Dec 23, 2025 by simonpasquier Loading…
4
OTA-1604: migrate ocp-46922 from otp to cvo repo jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#1279 opened Dec 23, 2025 by jiajliu Loading…
8
OCPBUGS-69974: Updating cluster-version-operator-container image to be consistent with ART for 4.22 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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. 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. staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead). verified Signifies that the PR passed pre-merge verification criteria
#1277 opened Dec 19, 2025 by openshift-bot Loading…
@wking
14
OTA-1787: pkg: Update Upgradeable condition to explicitly mention major version updates 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.
#1276 opened Dec 18, 2025 by wking Loading…
@DavidHurta
17
OCPSTRAT-2485: Introduce feature gate based inclusion/exclusion of manifests jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#1273 opened Dec 17, 2025 by JoelSpeed Loading…
19
NO-JIRA: hack/build-image.sh: Update Dockerfile reference 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. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria
#1272 opened Dec 11, 2025 by DavidHurta Loading…
@wking
11
OCPBUGS-66898: Implement mTLS authentication and authorization for CVO metrics endpoint 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/severity-moderate Referenced Jira bug's severity is moderate 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.
#1271 opened Dec 10, 2025 by DavidHurta Loading…
34
NO-JIRA: Introduce oc-cli for e2e 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. verified Signifies that the PR passed pre-merge verification criteria
#1267 opened Nov 28, 2025 by hongkailiu Loading…
@JianLi-RH
50
[WIP] OCPBUGS-65621: add dedicated service account to crb, cvo and version pod do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/severity-critical Referenced Jira bug's severity is critical 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.
#1266 opened Nov 28, 2025 by ehearne-redhat Loading…
47
[release-4.20] OCPBUGS-64828: lib/resourcemerge: Add support for hostUsers flag 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. 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.
#1259 opened Nov 7, 2025 by openshift-cherrypick-robot Loading…
@wking
7
NO-ISSUE: OTA-1605 Create first e2e test OCP-42543 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.
#1249 opened Oct 22, 2025 by JianLi-RH Loading…
@hongkailiu @DavidHurta
149
OCPBUGS-62858: pkg/cvo/metrics: Add a new --serving-client-certificate-authorities-file option 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. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#1240 opened Oct 8, 2025 by wking Loading…
9
WIP: CVO configuration: Minor refactoring and changes approved Indicates a PR has been approved by an approver from all required OWNERS files. 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.
#1234 opened Sep 24, 2025 by DavidHurta Loading…
7
WIP: CVO configuration: Introduce a config provider interface approved Indicates a PR has been approved by an approver from all required OWNERS files. 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.
#1233 opened Sep 23, 2025 by DavidHurta Loading…
6
MON-4358: Bump API version to include monitoring capability do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. 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. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#1229 opened Sep 3, 2025 by rexagod • Draft
7
hack/cluster-version-util/task_graph: Task-node granularity approved Indicates a PR has been approved by an approver from all required OWNERS files. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
#1221 opened Aug 6, 2025 by wking Loading…
6
WIP: pkg/payload/task: Include filename in Task.String approved Indicates a PR has been approved by an approver from all required OWNERS files. 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.
#1219 opened Aug 4, 2025 by wking Loading…
6
Draft: test changes not the final outputs 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.
#1218 opened Aug 1, 2025 by dis016 Loading…
37
ProTip! Add no:assignee to see everything that’s not assigned.