Skip to content

Pull requests: openshift/cluster-capi-operator

New pull request New
35 Open 440 Closed
35 Open 440 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

NO-JIRA: Fix 2 failures in ci jobs jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#485 opened Mar 3, 2026 by sunzhaohua2 Loading…
6
NO-JIRA: e2e: improve failure diagnostics 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.
#484 opened Mar 2, 2026 by theobarberbany Loading…
@JoelSpeed
19
OCPBUGS-77545: Updating ose-cluster-capi-operator-container image to be consistent with ART for 4.22 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. verified Signifies that the PR passed pre-merge verification criteria
#483 opened Mar 2, 2026 by openshift-bot Loading…
@theobarberbany
10
OSASINFRA-3980: Re-add openstack credentials request 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
#478 opened Feb 27, 2026 by stephenfin Loading…
@mdbooth
17
DNM: All of CompatibilityRequirements for testing do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.
#477 opened Feb 27, 2026 by JoelSpeed • Draft
4
OCPCLOUD-3369: Implement RequiredVersions functionality for CompatibilitySchema 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.
#471 opened Feb 25, 2026 by JoelSpeed • Draft
5
OCPCLOUD-3350: Revision controller 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. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#469 opened Feb 20, 2026 by mdbooth Loading…
1 task
@JoelSpeed
80
OCPCLOUD-3184: Implement object schema pruning for compatibility requirements 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.
#464 opened Feb 16, 2026 by JoelSpeed • Draft
5
NO-JIRA: manifests-gen: use real version for cluster-capi-operator dependency 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. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. verified Signifies that the PR passed pre-merge verification criteria
#462 opened Feb 16, 2026 by RadekManak Loading…
@theobarberbany
13
OCPCLOUD-3005,OCPCLOUD-3186,OCPCLOUD-3367: Implement validation webhook for custom resource admission jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#461 opened Feb 13, 2026 by JoelSpeed Loading…
69
OCPCLOUD-3357: Tests for networkpolicies in capi jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#456 opened Feb 6, 2026 by miyadav Loading…
23
SPLAT-2410: Introduce Cluster API for OpenShift Installations on vSphere 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.
#455 opened Feb 5, 2026 by AnnaZivkovic Loading…
@damdo @jcpowermac
40
OCPCLOUD-3354: Optimize migration e2e to reduce running time 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.
#451 opened Feb 2, 2026 by sunzhaohua2 Loading…
@nrb @RadekManak
32
DNM: WIP: tls: use centralized TLS profile do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#448 opened Jan 23, 2026 by damdo • Draft
7
OCPCLOUD-2992: added tests for OCP-86581 capi machine vaps 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.
#443 opened Jan 9, 2026 by miyadav Loading…
@mdbooth @RadekManak @sunzhaohua2
18
OCPCLOUD-2993: support network interface and no MAPI ebs volumesize conversion jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#431 opened Dec 16, 2025 by huali9 Loading…
8
OCPCLOUD-2641,OCPCLOUD-3188: add e2e tests to verify ValidatingAdmissionPolicy 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.
#415 opened Dec 1, 2025 by sunzhaohua2 Loading…
@nrb @theobarberbany
18
OCPCLOUD-3041: Created Cluster-api-tests-ext command for origin e2e jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
#413 opened Nov 26, 2025 by sunzhaohua2 Loading…
@damdo @theobarberbany
78
OCPBUGS-63411: machinesync: Create Cluster API InfraMachine if not exists while Cluster API Machine exists 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/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.
#402 opened Oct 30, 2025 by chrischdi Loading…
@nrb
61
OCPCLOUD-2992: machine update 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.
#400 opened Oct 28, 2025 by huali9 Loading…
@nrb @chrischdi
@damdo @theobarberbany
53
OCPBUGS-63320: Fix MAPI->CAPI conversion not adding ControlPlane label approved Indicates a PR has been approved by an approver from all required OWNERS files. 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. lgtm Indicates that a PR is ready to be merged.
#399 opened Oct 24, 2025 by RadekManak Loading…
@damdo
27
Sync master-user-data secret do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#397 opened Oct 24, 2025 by RadekManak • Draft
17
Nutanix: Machine API Provider to Cluster API Provider 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.
#395 opened Oct 23, 2025 by abhay-nutanix Loading…
@jcpowermac
24
OCPCLOUD-3355: e2e testing automation: Implement Status Syncing for MAPI/CAPI migration 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.
#387 opened Oct 14, 2025 by sunzhaohua2 Loading…
@nrb @damdo @theobarberbany
81
NO-JIRA: Add initial support for CAPI Nutanix provider 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.
#383 opened Oct 10, 2025 by abhay-nutanix Loading…
@mdbooth @jcpowermac
102
ProTip! Type g i on any issue or pull request to go back to the issue listing page.