Skip to content

NO-JIRA: Add MachineAPIMigrationVSphere feature gate for DevPreview#2739

Open
AnnaZivkovic wants to merge 1 commit intoopenshift:masterfrom
AnnaZivkovic:create-new-vsphere-feature-gate
Open

NO-JIRA: Add MachineAPIMigrationVSphere feature gate for DevPreview#2739
AnnaZivkovic wants to merge 1 commit intoopenshift:masterfrom
AnnaZivkovic:create-new-vsphere-feature-gate

Conversation

@AnnaZivkovic
Copy link
Contributor

Introduces the MachineAPIMigrationVSphere feature gate to enable Machine API to Cluster API migration support specifically for vSphere clusters. This feature gate is currently enabled exclusively within the DevPreviewNoUpgrade feature set.

Currently, the MAPI-to-CAPI conversion logic for vSphere relies on FeatureGateClusterAPIMachineManagementVSphere. To align with the new platform-specific feature gate pattern for migrations, we are introducing this dedicated gate. Once this PR merges, we will transition the vSphere conversion logic over to use MachineAPIMigrationVSphere.

This relates to the work here #2730

Enables the Machine API migration feature for vSphere platform in DevPreviewNoUpgrade feature set to support migrating from Machine API to Cluster API on vSphere clusters.
@openshift-ci-robot
Copy link

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 3, 2026

Hello @AnnaZivkovic! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

@coderabbitai
Copy link

coderabbitai bot commented Mar 3, 2026

📝 Walkthrough

Walkthrough

This pull request introduces a new feature gate named MachineAPIMigrationVSphere across the codebase. A new public feature gate definition is added in the features Go package with configuration for the SPLAT Jira component and Dev Preview enablement. The feature gate is then registered in feature gate manifest files for both Hypershift and SelfManagedHA deployment configurations, with varying enabled/disabled states across Default, DevPreviewNoUpgrade, OKD, and TechPreviewNoUpgrade scenarios. A corresponding entry is added to the features documentation table.

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description check ✅ Passed The description is directly related to the changeset, explaining the purpose of the new feature gate, its scope, and its relationship to existing code and future work.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check ✅ Passed The title accurately describes the main change: adding a new feature gate 'MachineAPIMigrationVSphere' configured for DevPreview, which is the core purpose of the PR.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.


Comment @coderabbitai help to get the list of available commands and usage tips.

@qodo-code-review
Copy link

Review Summary by Qodo

Add MachineAPIMigrationVSphere feature gate for DevPreview

✨ Enhancement

Grey Divider

Walkthroughs

Description
• Introduces MachineAPIMigrationVSphere feature gate for vSphere platform
• Enables Machine API to Cluster API migration support in DevPreviewNoUpgrade
• Updates feature gate manifests across multiple deployment configurations
• Registers gate with SPLAT component and jcpowermac contact person
Diagram
flowchart LR
  A["Feature Gate Definition"] -->|"Registered in"| B["features.go"]
  B -->|"Documented in"| C["features.md"]
  B -->|"Enabled in"| D["DevPreviewNoUpgrade Manifests"]
  D -->|"Includes"| E["Hypershift & SelfManagedHA Configs"]
Loading

Grey Divider

File Changes

1. features/features.go ✨ Enhancement +7/-0

Define MachineAPIMigrationVSphere feature gate

features/features.go


2. features.md 📝 Documentation +1/-0

Document MachineAPIMigrationVSphere in feature matrix

features.md


3. payload-manifests/featuregates/featureGate-4-10-Hypershift-Default.yaml ⚙️ Configuration changes +3/-0

Add MachineAPIMigrationVSphere to Default manifest

payload-manifests/featuregates/featureGate-4-10-Hypershift-Default.yaml


View more (7)
4. payload-manifests/featuregates/featureGate-4-10-Hypershift-DevPreviewNoUpgrade.yaml ⚙️ Configuration changes +3/-0

Add MachineAPIMigrationVSphere to DevPreviewNoUpgrade manifest

payload-manifests/featuregates/featureGate-4-10-Hypershift-DevPreviewNoUpgrade.yaml


5. payload-manifests/featuregates/featureGate-4-10-Hypershift-OKD.yaml ⚙️ Configuration changes +3/-0

Add MachineAPIMigrationVSphere to OKD manifest

payload-manifests/featuregates/featureGate-4-10-Hypershift-OKD.yaml


6. payload-manifests/featuregates/featureGate-4-10-Hypershift-TechPreviewNoUpgrade.yaml ⚙️ Configuration changes +3/-0

Add MachineAPIMigrationVSphere to TechPreviewNoUpgrade manifest

payload-manifests/featuregates/featureGate-4-10-Hypershift-TechPreviewNoUpgrade.yaml


7. payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-Default.yaml ⚙️ Configuration changes +3/-0

Add MachineAPIMigrationVSphere to SelfManagedHA Default manifest

payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-Default.yaml


8. payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-DevPreviewNoUpgrade.yaml ⚙️ Configuration changes +3/-0

Add MachineAPIMigrationVSphere to SelfManagedHA DevPreviewNoUpgrade manifest

payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-DevPreviewNoUpgrade.yaml


9. payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-OKD.yaml ⚙️ Configuration changes +3/-0

Add MachineAPIMigrationVSphere to SelfManagedHA OKD manifest

payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-OKD.yaml


10. payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-TechPreviewNoUpgrade.yaml ⚙️ Configuration changes +3/-0

Add MachineAPIMigrationVSphere to SelfManagedHA TechPreviewNoUpgrade manifest

payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-TechPreviewNoUpgrade.yaml


Grey Divider

Qodo Logo

@qodo-code-review
Copy link

qodo-code-review bot commented Mar 3, 2026

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Grey Divider

ⓘ The new review experience is currently in Beta. Learn more

Grey Divider

Qodo Logo

@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Mar 3, 2026
@openshift-ci openshift-ci bot requested review from JoelSpeed and everettraven March 3, 2026 22:47
@AnnaZivkovic
Copy link
Contributor Author

@mdbooth Is this what you were asking for here?

@JoelSpeed
Copy link
Contributor

/lgtm

/hold for @mdbooth

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 4, 2026
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 4, 2026
@openshift-ci-robot
Copy link

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-ovn
/test e2e-aws-ovn-hypershift
/test e2e-aws-ovn-hypershift-conformance
/test e2e-aws-ovn-techpreview
/test e2e-aws-serial-1of2
/test e2e-aws-serial-2of2
/test e2e-aws-serial-techpreview-1of2
/test e2e-aws-serial-techpreview-2of2
/test e2e-azure
/test e2e-gcp
/test e2e-upgrade
/test e2e-upgrade-out-of-change
/test minor-e2e-upgrade-minor

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 4, 2026
Copy link
Contributor

@mdbooth mdbooth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 4, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 4, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed, mdbooth

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 4, 2026

@AnnaZivkovic: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-ovn-hypershift 6a76ae3 link true /test e2e-aws-ovn-hypershift
ci/prow/e2e-aws-ovn-hypershift-conformance 6a76ae3 link true /test e2e-aws-ovn-hypershift-conformance

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@AnnaZivkovic AnnaZivkovic changed the title Add MachineAPIMigrationVSphere feature gate for DevPreview NO-JIRA: Add MachineAPIMigrationVSphere feature gate for DevPreview Mar 4, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 4, 2026
@openshift-ci-robot
Copy link

@AnnaZivkovic: This pull request explicitly references no jira issue.

Details

In response to this:

Introduces the MachineAPIMigrationVSphere feature gate to enable Machine API to Cluster API migration support specifically for vSphere clusters. This feature gate is currently enabled exclusively within the DevPreviewNoUpgrade feature set.

Currently, the MAPI-to-CAPI conversion logic for vSphere relies on FeatureGateClusterAPIMachineManagementVSphere. To align with the new platform-specific feature gate pattern for migrations, we are introducing this dedicated gate. Once this PR merges, we will transition the vSphere conversion logic over to use MachineAPIMigrationVSphere.

This relates to the work here #2730

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@AnnaZivkovic
Copy link
Contributor Author

/retest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants