Goal

Have a clean and clear feature set in kubevirt/kubevirt. Eliminate year-old feature flags. After 3 releases, KubeVirt features should either mature or removed.

User Stories

• As a cluster admin, I want to use feature-gated features without fearing they may disappear in the future. After a year of experimentation, a feature gate should go. Either to feature maturity or to feature removal.

Non-Requirements

• List of things not included in this epic, to alleviate any doubt raised during the grooming process.

Notes

• Upstream feature transition: https://github.com/kubevirt/community/blob/main/design-proposals/feature-lifecycle.md#release-stage-transition-table
• fdeutsch@redhat.com's call for action: https://docs.google.com/presentation/d/1naZ8t8akwKTsMwO_0YdWJAA4-3CmOneyqPUFFzqPRpA/edit#slide=id.g2e5bc199ee8_0_34