Skip to content

Pull requests: openshift/cluster-capi-operator

New pull request New
22 Open 499 Closed
22 Open 499 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

fix: conversion: handle HTTPProtocolIPv6 in AWS for CAPA v2.11.0 pipeline-auto
#531 opened Apr 26, 2026 by damdo Member Loading…
7
OCPCLOUD-3429: Mount provider images with image volumes jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. pipeline-auto
#527 opened Apr 24, 2026 by mdbooth Contributor Loading…
53
NO-JIRA: Add Dockerfile.e2e jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. pipeline-auto
#526 opened Apr 21, 2026 by mdbooth Contributor Loading…
27
NO-JIRA: manifests-gen: set scc annotation in providers Deployments spec 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.
#524 opened Apr 17, 2026 by damdo Member • Draft
7
OCPCLOUD-3373: Adds wildcard support for manifests-gen 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.
#521 opened Apr 13, 2026 by theobarberbany Contributor Loading…
@mdbooth @damdo
22
OCPCLOUD-2208: Add cluster-wide proxy support for CAPI controllers jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.
#517 opened Apr 2, 2026 by lunarwhite Contributor Loading…
3 tasks done
@mdbooth
20
OCPCLOUD-1645: Security: Configure RBAC for capi operator do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. 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.
#493 opened Mar 12, 2026 by sunzhaohua2 Contributor • Draft
32
DNM: NO-JIRA: Set admission failure policy to Fail 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.
#486 opened Mar 3, 2026 by JoelSpeed Contributor • Draft
9
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 Member 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.
#455 opened Feb 5, 2026 by AnnaZivkovic Loading…
@damdo @jcpowermac @vr4manta
117
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 Contributor Loading…
@nrb @RadekManak
32
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 Member Loading…
@mdbooth @RadekManak @sunzhaohua2
18
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 Contributor 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 Contributor Loading…
@mdbooth @damdo @theobarberbany
124
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 Contributor Loading…
@nrb
62
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.
#399 opened Oct 24, 2025 by RadekManak Contributor Loading…
@damdo
30
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. 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.
#397 opened Oct 24, 2025 by RadekManak Contributor • Draft
19
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 Contributor Loading…
@nrb @damdo @theobarberbany
81
NO-JIRA: Add initial support for CAPI Nutanix provider 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. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#383 opened Oct 10, 2025 by abhay-nutanix • Draft
@mdbooth @jcpowermac
108
OCPCLOUD-2998: implement synchronizedAPI 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.
#376 opened Oct 3, 2025 by RadekManak Contributor Loading…
@mdbooth
31
Add mapi -> capi migration subagent approved Indicates a PR has been approved by an approver from all required OWNERS files.
#369 opened Sep 26, 2025 by theobarberbany Contributor Loading…
@RadekManak
13
NO-JIRA: Expand CAPI to Cluster API and MAPI to Machine API 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. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
#272 opened Mar 14, 2025 by RadekManak Contributor Loading…
@damdo @theobarberbany
25
ProTip! Updated in the last three days: updated:>2026-04-23.