feat(vmpool): enable VirtualMachinePool in EE/SE+ without a feature gate#2621
Merged
Conversation
fl64
requested review from
Isteb4k,
goganat,
prismagod and
yaroslavborbat
as code owners
July 9, 2026 11:12
The VirtualMachinePool feature gate was an opt-in placeholder. As the feature has not been released yet, drop the gate before release so the resource is available in EE/SE+ out of the box and stays unavailable in CE — the same model as VolumeMigration/TargetMigration. Nothing to migrate: the gate never shipped. - gate becomes locked-on in EE/SE+, locked-off in CE (no user opt-in) - dropped from the user-facing featureGates enum - pool webhooks gated by edition in helm instead of the feature-gate list Controller/webhooks keep self-gating on the now-locked gate. Signed-off-by: Pavel Tishkov <pavel.tishkov@flant.com>
fl64
force-pushed
the
feat/vmpool/remove-feature-gate
branch
from
July 9, 2026 11:15
ed796f8 to
a3a4713
Compare
fl64
changed the title
yaroslavborbat
approved these changes
Jul 9, 2026
deckhouse-BOaTswain
pushed a commit
that referenced
this pull request
Jul 16, 2026
…ate (#2621) The VirtualMachinePool feature gate was an opt-in placeholder. As the feature has not been released yet, drop the gate before release so the resource is available in EE/SE+ out of the box and stays unavailable in CE — the same model as VolumeMigration/TargetMigration. Nothing to migrate: the gate never shipped. - gate becomes locked-on in EE/SE+, locked-off in CE (no user opt-in) - dropped from the user-facing featureGates enum - pool webhooks gated by edition in helm instead of the feature-gate list Controller/webhooks keep self-gating on the now-locked gate. Signed-off-by: Pavel Tishkov <pavel.tishkov@flant.com>
deckhouse-BOaTswain
pushed a commit
that referenced
this pull request
Jul 22, 2026
…ate (#2621) The VirtualMachinePool feature gate was an opt-in placeholder. As the feature has not been released yet, drop the gate before release so the resource is available in EE/SE+ out of the box and stays unavailable in CE — the same model as VolumeMigration/TargetMigration. Nothing to migrate: the gate never shipped. - gate becomes locked-on in EE/SE+, locked-off in CE (no user opt-in) - dropped from the user-facing featureGates enum - pool webhooks gated by edition in helm instead of the feature-gate list Controller/webhooks keep self-gating on the now-locked gate. Signed-off-by: Pavel Tishkov <pavel.tishkov@flant.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
VirtualMachinePool needed a feature gate to be turned on manually in the paid editions (EE/SE+). Since the resource has not been released yet, we remove that gate before release: VirtualMachinePool now works in EE/SE+ out of the box, and stays unavailable in CE (a paid-only feature). There is nothing for users to enable, and nothing to migrate — the gate never shipped.
Why do we need it, and what problem does it solve?
Requiring users to flip a feature gate adds friction with no benefit. Removing it before release means the resource just works in the editions that ship it.
What is the expected result?
In EE/SE+ VirtualMachinePool works without any feature-gate configuration; in CE it is not available. Users neither set nor see a VirtualMachinePool feature gate.
Checklist
Changelog entries