Skip to content

SPLAT-2320: vsphere vm-host zonal ga#2731

Open
jcpowermac wants to merge 1 commit intoopenshift:masterfrom
jcpowermac:vm-host-zonal-ga
Open

SPLAT-2320: vsphere vm-host zonal ga#2731
jcpowermac wants to merge 1 commit intoopenshift:masterfrom
jcpowermac:vm-host-zonal-ga

Conversation

@jcpowermac
Copy link
Contributor

This commit is to add the vSphere vm-host zonal feature to default (GA).

@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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 26, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 26, 2026

@jcpowermac: This pull request references SPLAT-2320 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

This commit is to add the vSphere vm-host zonal feature to default (GA).

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 26, 2026

Hello @jcpowermac! 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 Feb 26, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between a8b0a3d and 3757b1d.

⛔ Files ignored due to path filters (4)
  • config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_infrastructures-Default.crd.yaml is excluded by !**/zz_generated.crd-manifests/*
  • config/v1/zz_generated.crd-manifests/0000_10_config-operator_01_infrastructures-OKD.crd.yaml is excluded by !**/zz_generated.crd-manifests/*
  • machineconfiguration/v1/zz_generated.crd-manifests/0000_80_machine-config_01_controllerconfigs-Default.crd.yaml is excluded by !**/zz_generated.crd-manifests/*
  • machineconfiguration/v1/zz_generated.crd-manifests/0000_80_machine-config_01_controllerconfigs-OKD.crd.yaml is excluded by !**/zz_generated.crd-manifests/*
📒 Files selected for processing (10)
  • features.md
  • features/features.go
  • payload-manifests/crds/0000_10_config-operator_01_infrastructures-Default.crd.yaml
  • payload-manifests/crds/0000_10_config-operator_01_infrastructures-OKD.crd.yaml
  • payload-manifests/crds/0000_80_machine-config_01_controllerconfigs-Default.crd.yaml
  • payload-manifests/crds/0000_80_machine-config_01_controllerconfigs-OKD.crd.yaml
  • payload-manifests/featuregates/featureGate-4-10-Hypershift-Default.yaml
  • payload-manifests/featuregates/featureGate-4-10-Hypershift-OKD.yaml
  • payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-Default.yaml
  • payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-OKD.yaml
🚧 Files skipped from review as they are similar to previous changes (2)
  • features/features.go
  • payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-OKD.yaml

📝 Walkthrough

Walkthrough

The VSphereHostVMGroupZonal feature gate declaration was expanded to include inDefault() and inOKD() in addition to inTechPreviewNoUpgrade() and inDevPreviewNoUpgrade(). Feature-gate manifests for Hypershift and SelfManagedHA variants (Default and OKD) were updated to move VSphereHostVMGroupZonal from disabled to enabled. Multiple CRD OpenAPI schemas (infrastructures and controllerconfigs for Default and OKD) were updated to add two x-kubernetes-validations enforcing cross-field rules between zoneAffinity.type and regionAffinity.type. Features.md had the VSphereHostVMGroupZonal row relocated within a table without content changes.

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: promoting the vSphere vm-host zonal feature to GA (general availability) across all modified files.
Description check ✅ Passed The description is directly related to the changeset, accurately stating the purpose of adding the vSphere vm-host zonal feature to default (GA).
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ 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

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (2.5.0)

Error: build linters: unable to load custom analyzer "kubeapilinter": tools/_output/bin/kube-api-linter.so, plugin: not implemented
The command is terminated due to an error: build linters: unable to load custom analyzer "kubeapilinter": tools/_output/bin/kube-api-linter.so, plugin: not implemented


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

@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Feb 26, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 26, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign everettraven for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@jcpowermac
Copy link
Contributor Author

jcpowermac commented Feb 26, 2026

This promotion will be validated/approved by @sgaoshang since enabling this topology has been problematic using nested vSphere and we are not able to test this in our typical vSphere CI environments do to region/zone tagging requirements.

/assign @sgaoshang

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

🧹 Nitpick comments (1)
features/features.go (1)

183-189: Missing space after comma in enable() call.

Line 188 has inconsistent formatting compared to other feature gates in this file. There's a missing space after inOKD(), before inTechPreviewNoUpgrade().

🔧 Suggested fix for formatting consistency
 	FeatureGateVSphereHostVMGroupZonal = newFeatureGate("VSphereHostVMGroupZonal").
 					reportProblemsToJiraComponent("splat").
 					contactPerson("jcpowermac").
 					productScope(ocpSpecific).
 					enhancementPR("https://github.com/openshift/enhancements/pull/1677").
-					enable(inDefault(), inOKD(),inTechPreviewNoUpgrade(), inDevPreviewNoUpgrade()).
+					enable(inDefault(), inOKD(), inTechPreviewNoUpgrade(), inDevPreviewNoUpgrade()).
 					mustRegister()
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@features/features.go` around lines 183 - 189, The enable() call on
FeatureGateVSphereHostVMGroupZonal has inconsistent spacing (missing space after
the comma between inOKD() and inTechPreviewNoUpgrade()); update the enable(...)
invocation in the FeatureGateVSphereHostVMGroupZonal declaration to match file
formatting by adding a space after the comma so it reads inDefault(), inOKD(),
inTechPreviewNoUpgrade(), inDevPreviewNoUpgrade(), ensuring the rest of the
fluent chain (reportProblemsToJiraComponent, contactPerson, productScope,
enhancementPR, mustRegister) remains unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@features/features.go`:
- Around line 183-189: The enable() call on FeatureGateVSphereHostVMGroupZonal
has inconsistent spacing (missing space after the comma between inOKD() and
inTechPreviewNoUpgrade()); update the enable(...) invocation in the
FeatureGateVSphereHostVMGroupZonal declaration to match file formatting by
adding a space after the comma so it reads inDefault(), inOKD(),
inTechPreviewNoUpgrade(), inDevPreviewNoUpgrade(), ensuring the rest of the
fluent chain (reportProblemsToJiraComponent, contactPerson, productScope,
enhancementPR, mustRegister) remains unchanged.

ℹ️ Review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between f733385 and f10ee89.

📒 Files selected for processing (6)
  • features.md
  • features/features.go
  • payload-manifests/featuregates/featureGate-4-10-Hypershift-Default.yaml
  • payload-manifests/featuregates/featureGate-4-10-Hypershift-OKD.yaml
  • payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-Default.yaml
  • payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-OKD.yaml

@openshift-ci openshift-ci bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 26, 2026
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

🧹 Nitpick comments (1)
features/features.go (1)

181-187: Minor formatting inconsistency: missing space after comma.

Line 186 is missing a space between inOKD(), and inTechPreviewNoUpgrade(), which is inconsistent with the formatting used elsewhere in this file (e.g., lines 82, 91, 107, 194).

✏️ Suggested fix
 	FeatureGateVSphereHostVMGroupZonal = newFeatureGate("VSphereHostVMGroupZonal").
 						reportProblemsToJiraComponent("splat").
 						contactPerson("jcpowermac").
 						productScope(ocpSpecific).
 						enhancementPR("https://github.com/openshift/enhancements/pull/1677").
-						enable(inDefault(), inOKD(),inTechPreviewNoUpgrade(), inDevPreviewNoUpgrade()).
+						enable(inDefault(), inOKD(), inTechPreviewNoUpgrade(), inDevPreviewNoUpgrade()).
 						mustRegister()
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@features/features.go` around lines 181 - 187, The enable(...) call for
FeatureGateVSphereHostVMGroupZonal has a missing space after the comma between
inOKD() and inTechPreviewNoUpgrade(); update the enable invocation on
FeatureGateVSphereHostVMGroupZonal so it reads enable(inDefault(), inOKD(),
inTechPreviewNoUpgrade(), inDevPreviewNoUpgrade()) — i.e., insert a single space
after the comma to match the file's existing formatting for other feature gates.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@features/features.go`:
- Around line 181-187: The enable(...) call for
FeatureGateVSphereHostVMGroupZonal has a missing space after the comma between
inOKD() and inTechPreviewNoUpgrade(); update the enable invocation on
FeatureGateVSphereHostVMGroupZonal so it reads enable(inDefault(), inOKD(),
inTechPreviewNoUpgrade(), inDevPreviewNoUpgrade()) — i.e., insert a single space
after the comma to match the file's existing formatting for other feature gates.

ℹ️ Review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between f10ee89 and 1b93745.

📒 Files selected for processing (6)
  • features.md
  • features/features.go
  • payload-manifests/featuregates/featureGate-4-10-Hypershift-Default.yaml
  • payload-manifests/featuregates/featureGate-4-10-Hypershift-OKD.yaml
  • payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-Default.yaml
  • payload-manifests/featuregates/featureGate-4-10-SelfManagedHA-OKD.yaml
🚧 Files skipped from review as they are similar to previous changes (1)
  • payload-manifests/featuregates/featureGate-4-10-Hypershift-OKD.yaml

This commit is to add the vSphere vm-host zonal feature to default (GA).
@openshift-ci openshift-ci bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Feb 27, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 27, 2026

@jcpowermac: The following test 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/verify-feature-promotion 3757b1d link true /test verify-feature-promotion

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.

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

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants