Skip to content

Fix feature gate description/phase mismatches for decentralizedLiveMigration and incrementalBackup - #4463

Merged
kubevirt-prow[bot] merged 1 commit into
kubevirt:mainfrom
hmeir:fix-featuregate-description-mismatch
Aug 3, 2026
Merged

kubevirt-prow[bot] merged 1 commit into
kubevirt:mainfrom
hmeir:fix-featuregate-description-mismatch

Conversation

@hmeir

@hmeir hmeir commented Jul 30, 2026 •

Copy link
Copy Markdown
Contributor

What this PR does / why we need it:
decentralizedLiveMigration (beta) incorrectly said "Developer Preview" instead of "Tech Preview". incrementalBackup (alpha) incorrectly said "Tech Preview" instead of "Developer Preview".

Reviewer Checklist

Reviewers are supposed to review the PR for every aspect below one by one. To check an item means the PR is either "OK" or "Not Applicable" in terms of that item. All items are supposed to be checked before merging a PR.

  • PR Message
  • Commit Messages
  • How to test
  • Unit Tests
  • Functional Tests
  • User Documentation
  • Developer Documentation
  • Upgrade Scenario
  • Uninstallation Scenario
  • Backward Compatibility
  • Troubleshooting Friendly

Jira Ticket:

https://redhat.atlassian.net/browse/CNV-94271

Release note:

None

@kubevirt-prow kubevirt-prow Bot added dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Jul 30, 2026
@kubevirt-prow

kubevirt-prow Bot commented Jul 30, 2026

Copy link
Copy Markdown

Hi @hmeir. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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.

@openshift-ci openshift-ci Bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Jul 30, 2026
@openshift-ci

openshift-ci Bot commented Jul 30, 2026

Copy link
Copy Markdown

Hi @hmeir. Thanks for your PR.

I'm waiting for a kubevirt member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@kubevirt-prow
kubevirt-prow Bot requested review from nunnatsa and tiraboschi July 30, 2026 12:28
@kubevirt-prow kubevirt-prow Bot added the size/S label Jul 30, 2026
@coderabbitai

coderabbitai Bot commented Jul 30, 2026 •

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 89b31e28-93cb-4e67-851c-6c2d5f26c83f

📥 Commits

Reviewing files that changed from the base of the PR and between 5020d64 and 40c3c60.

⛔ Files ignored due to path filters (2)
  • api/v1/zz_generated.openapi.go is excluded by !**/zz_generated.*
  • api/v1beta1/zz_generated.openapi.go is excluded by !**/zz_generated.*
📒 Files selected for processing (13)
  • api/v1/hyperconverged_types.go
  • api/v1beta1/hyperconverged_types.go
  • config/crd/bases/hco.kubevirt.io_hyperconvergeds.yaml
  • deploy/crds/hco00.crd.yaml
  • deploy/index-image/community-kubevirt-hyperconverged/1.19.0/manifests/hco00.crd.yaml
  • deploy/olm-catalog/community-kubevirt-hyperconverged/1.19.0/manifests/hco00.crd.yaml
  • docs/api-v1beta1.md
  • docs/api.md
  • docs/cluster-configuration-v1beta1-api.md
  • docs/cluster-configuration.md
  • pkg/featuregatedetails/feature-gates.json
  • tools/csv-merger/generated-crd.yaml
  • tools/manifest-templator/generated-crd.yaml
🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

  • kubevirt/kubevirt (manual)
  • kubevirt/hyperconverged-cluster-operator (manual)
  • kubevirt/monitoring (manual)
🚧 Files skipped from review as they are similar to previous changes (11)
  • deploy/index-image/community-kubevirt-hyperconverged/1.19.0/manifests/hco00.crd.yaml
  • deploy/olm-catalog/community-kubevirt-hyperconverged/1.19.0/manifests/hco00.crd.yaml
  • config/crd/bases/hco.kubevirt.io_hyperconvergeds.yaml
  • api/v1/hyperconverged_types.go
  • docs/api.md
  • tools/csv-merger/generated-crd.yaml
  • api/v1beta1/hyperconverged_types.go
  • pkg/featuregatedetails/feature-gates.json
  • docs/api-v1beta1.md
  • deploy/crds/hco00.crd.yaml
  • tools/manifest-templator/generated-crd.yaml

📝 Walkthrough

Walkthrough

Updated preview maturity labels for DecentralizedLiveMigration and IncrementalBackup across API documentation, feature-gate metadata, CRD descriptions, and generated manifests. No API fields, types, validation, serialization, or runtime logic changed.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

Warning

Review ran into problems

🔥 Problems

Linked repositories: Your configuration references 13 linked repositories, but your current plan allows 10. Analyzed kubevirt/kubevirt, kubevirt/containerized-data-importer, kubevirt/ssp-operator, kubevirt/cluster-network-addons-operator, kubevirt/hostpath-provisioner-operator, kubevirt/application-aware-quota, kubevirt/managed-tenant-quota, kubevirt/hyperconverged-cluster-operator, kubevirt/monitoring, kubevirt/community, skipped kubevirt/enhancements, kubevirt/project-infra, kubevirt/kubevirtci.


Linked repositories: Public OSS repositories can only analyze public repositories installed in this organization. Analyzed kubevirt/kubevirt, kubevirt/hyperconverged-cluster-operator, kubevirt/monitoring, skipped kubevirt/containerized-data-importer, kubevirt/ssp-operator, kubevirt/cluster-network-addons-operator, kubevirt/hostpath-provisioner-operator, kubevirt/application-aware-quota, kubevirt/managed-tenant-quota, kubevirt/community.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@nunnatsa

Copy link
Copy Markdown
Collaborator

/ok-to-test

@openshift-ci openshift-ci Bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jul 30, 2026
@kubevirt-prow kubevirt-prow Bot added release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Jul 30, 2026
@coveralls

Copy link
Copy Markdown
Collaborator

Coverage Report for CI Build 30542681432

Warning

Build has drifted: This PR's base is out of sync with its target branch, so coverage data may include unrelated changes.
Quick fix: rebase this PR. Learn more →

Coverage remained the same at 85.618%

Details

  • Coverage remained the same as the base build.
  • Patch coverage: No coverable lines changed in this PR.
  • No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.


Coverage Stats

Coverage Status
Relevant Lines: 14066
Covered Lines: 12043
Line Coverage: 85.62%
Coverage Strength: 2.33 hits per line

💛 - Coveralls

@hco-bot

hco-bot commented Jul 30, 2026

Copy link
Copy Markdown
Collaborator

hco-e2e-consecutive-operator-sdk-upgrades-azure lane succeeded.
/override ci/prow/hco-e2e-consecutive-operator-sdk-upgrades-aws
hco-e2e-operator-sdk-azure lane succeeded.
/override ci/prow/hco-e2e-operator-sdk-gcp
hco-e2e-operator-sdk-azure lane succeeded.
/override ci/prow/hco-e2e-operator-sdk-aws
hco-e2e-upgrade-prev-operator-sdk-azure lane succeeded.
/override ci/prow/hco-e2e-upgrade-prev-operator-sdk-aws
hco-e2e-upgrade-operator-sdk-sno-azure lane succeeded.
/override ci/prow/hco-e2e-upgrade-operator-sdk-sno-aws

@kubevirt-prow

kubevirt-prow Bot commented Jul 30, 2026

Copy link
Copy Markdown

@hco-bot: Overrode contexts on behalf of hco-bot: ci/prow/hco-e2e-consecutive-operator-sdk-upgrades-aws, ci/prow/hco-e2e-operator-sdk-aws, ci/prow/hco-e2e-operator-sdk-gcp, ci/prow/hco-e2e-upgrade-operator-sdk-sno-aws, ci/prow/hco-e2e-upgrade-prev-operator-sdk-aws

Details

In response to this:

hco-e2e-consecutive-operator-sdk-upgrades-azure lane succeeded.
/override ci/prow/hco-e2e-consecutive-operator-sdk-upgrades-aws
hco-e2e-operator-sdk-azure lane succeeded.
/override ci/prow/hco-e2e-operator-sdk-gcp
hco-e2e-operator-sdk-azure lane succeeded.
/override ci/prow/hco-e2e-operator-sdk-aws
hco-e2e-upgrade-prev-operator-sdk-azure lane succeeded.
/override ci/prow/hco-e2e-upgrade-prev-operator-sdk-aws
hco-e2e-upgrade-operator-sdk-sno-azure lane succeeded.
/override ci/prow/hco-e2e-upgrade-operator-sdk-sno-aws

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.

@hco-bot

hco-bot commented Jul 30, 2026

Copy link
Copy Markdown
Collaborator

hco-e2e-operator-sdk-azure lane succeeded.
/override ci/prow/hco-e2e-operator-sdk-aws

@kubevirt-prow

kubevirt-prow Bot commented Jul 30, 2026

Copy link
Copy Markdown

@hco-bot: Overrode contexts on behalf of hco-bot: ci/prow/hco-e2e-operator-sdk-aws

Details

In response to this:

hco-e2e-operator-sdk-azure lane succeeded.
/override ci/prow/hco-e2e-operator-sdk-aws

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.

@hco-bot

hco-bot commented Jul 30, 2026

Copy link
Copy Markdown
Collaborator

hco-e2e-kv-smoke-azure lane succeeded.
/override ci/prow/hco-e2e-kv-smoke-gcp

@kubevirt-prow

kubevirt-prow Bot commented Jul 30, 2026

Copy link
Copy Markdown

@hco-bot: Overrode contexts on behalf of hco-bot: ci/prow/hco-e2e-kv-smoke-gcp

Details

In response to this:

hco-e2e-kv-smoke-azure lane succeeded.
/override ci/prow/hco-e2e-kv-smoke-gcp

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.

@nunnatsa

nunnatsa commented Aug 2, 2026

Copy link
Copy Markdown
Collaborator

@hmeir thanks for this PR!

please notice that should not change the featureGates field comment in v1. It is auto generated from pkg/featuregatedetails/feature-gates.json, which is the source of truth. Only modify this file for v1.

Please don't forget to run make build-manifests and make generate-docs for all the auto generated CRD files and doc files.

@hmeir
hmeir force-pushed the fix-featuregate-description-mismatch branch from 907afbf to 5020d64 Compare August 3, 2026 08:10
@kubevirt-prow kubevirt-prow Bot added size/M and removed size/S labels Aug 3, 2026

@nunnatsa nunnatsa left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Please also check cluster-configuration-v1beta1-api.md and cluster-configuration.md

@hco-bot

hco-bot commented Aug 3, 2026

Copy link
Copy Markdown
Collaborator

hco-e2e-upgrade-prev-operator-sdk-sno-azure lane succeeded.
/override ci/prow/hco-e2e-upgrade-prev-operator-sdk-sno-aws
hco-e2e-operator-sdk-azure lane succeeded.
/override ci/prow/hco-e2e-operator-sdk-gcp
hco-e2e-operator-sdk-azure lane succeeded.
/override ci/prow/hco-e2e-operator-sdk-aws

@kubevirt-prow

kubevirt-prow Bot commented Aug 3, 2026

Copy link
Copy Markdown

@hco-bot: Overrode contexts on behalf of hco-bot: ci/prow/hco-e2e-operator-sdk-aws, ci/prow/hco-e2e-operator-sdk-gcp, ci/prow/hco-e2e-upgrade-prev-operator-sdk-sno-aws

Details

In response to this:

hco-e2e-upgrade-prev-operator-sdk-sno-azure lane succeeded.
/override ci/prow/hco-e2e-upgrade-prev-operator-sdk-sno-aws
hco-e2e-operator-sdk-azure lane succeeded.
/override ci/prow/hco-e2e-operator-sdk-gcp
hco-e2e-operator-sdk-azure lane succeeded.
/override ci/prow/hco-e2e-operator-sdk-aws

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.

…gration and incrementalBackup

decentralizedLiveMigration (beta) incorrectly said "Developer Preview" instead of "Tech Preview".
incrementalBackup (alpha) incorrectly said "Tech Preview" instead of "Developer Preview".

Signed-off-by: Harel Meir <hmeir@redhat.com>
@hmeir
hmeir force-pushed the fix-featuregate-description-mismatch branch from 5020d64 to 40c3c60 Compare August 3, 2026 10:06
@sonarqubecloud

sonarqubecloud Bot commented Aug 3, 2026

Copy link
Copy Markdown

@openshift-ci

openshift-ci Bot commented Aug 3, 2026

Copy link
Copy Markdown

@hmeir: 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/hco-e2e-upgrade-operator-sdk-sno-aws 40c3c60 link false /test hco-e2e-upgrade-operator-sdk-sno-aws
ci/prow/hco-e2e-kv-smoke-gcp 40c3c60 link true /test hco-e2e-kv-smoke-gcp
ci/prow/hco-e2e-operator-sdk-gcp 40c3c60 link true /test hco-e2e-operator-sdk-gcp
ci/prow/hco-e2e-upgrade-prev-operator-sdk-aws 40c3c60 link true /test hco-e2e-upgrade-prev-operator-sdk-aws

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.

@hco-bot

hco-bot commented Aug 3, 2026

Copy link
Copy Markdown
Collaborator

hco-e2e-upgrade-prev-operator-sdk-azure lane succeeded.
/override ci/prow/hco-e2e-upgrade-prev-operator-sdk-aws
hco-e2e-operator-sdk-azure, hco-e2e-operator-sdk-aws lanes succeeded.
/override ci/prow/hco-e2e-operator-sdk-gcp
hco-e2e-upgrade-operator-sdk-sno-azure lane succeeded.
/override ci/prow/hco-e2e-upgrade-operator-sdk-sno-aws

@kubevirt-prow

kubevirt-prow Bot commented Aug 3, 2026

Copy link
Copy Markdown

@hco-bot: Overrode contexts on behalf of hco-bot: ci/prow/hco-e2e-operator-sdk-gcp, ci/prow/hco-e2e-upgrade-operator-sdk-sno-aws, ci/prow/hco-e2e-upgrade-prev-operator-sdk-aws

Details

In response to this:

hco-e2e-upgrade-prev-operator-sdk-azure lane succeeded.
/override ci/prow/hco-e2e-upgrade-prev-operator-sdk-aws
hco-e2e-operator-sdk-azure, hco-e2e-operator-sdk-aws lanes succeeded.
/override ci/prow/hco-e2e-operator-sdk-gcp
hco-e2e-upgrade-operator-sdk-sno-azure lane succeeded.
/override ci/prow/hco-e2e-upgrade-operator-sdk-sno-aws

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.

@hco-bot

hco-bot commented Aug 3, 2026

Copy link
Copy Markdown
Collaborator

hco-e2e-kv-smoke-azure lane succeeded.
/override ci/prow/hco-e2e-kv-smoke-gcp

@kubevirt-prow

kubevirt-prow Bot commented Aug 3, 2026

Copy link
Copy Markdown

@hco-bot: Overrode contexts on behalf of hco-bot: ci/prow/hco-e2e-kv-smoke-gcp

Details

In response to this:

hco-e2e-kv-smoke-azure lane succeeded.
/override ci/prow/hco-e2e-kv-smoke-gcp

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.

@nunnatsa

nunnatsa commented Aug 3, 2026

Copy link
Copy Markdown
Collaborator

/lgtm
/approve

@kubevirt-prow kubevirt-prow Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 3, 2026
@kubevirt-prow

kubevirt-prow Bot commented Aug 3, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nunnatsa

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

@kubevirt-prow kubevirt-prow Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 3, 2026
@kubevirt-prow
kubevirt-prow Bot merged commit b532872 into kubevirt:main Aug 3, 2026
32 checks passed
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. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note. size/M

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants