XML

Word

Printable

Epic Name:
cnv-vm-console-proxy-lifecycle
Acceptance Criteria:
Hide

comply with https://github.com/kubevirt/community/blob/main/design-proposals/feature-lifecycle.md, especially

removing the feature gate

add a config option to deploy the vm-console-proxy, disabled by default

API is beta or ga, not alpha
Show
comply with https://github.com/kubevirt/community/blob/main/design-proposals/feature-lifecycle.md, especially removing the feature gate add a config option to deploy the vm-console-proxy, disabled by default API is beta or ga, not alpha
Current Status:
Green
Feature Link:
CNV-38613 - 2024 Code Quality
Parent Link:
CNV-386132024 Code Quality
Hierarchy Progress Bar:

0% To Do, 0% In Progress, 100% Done
Ready-Ready:

dev-ready, doc-ready, po-ready, qe-ready, ux-ready
Status Summary:

Hide

on track...

Show
on track...
Product Documentation Required:
Yes
Target Version:

CNV v4.18.0

Goal

According to the new feautre life cycle, optional features like the vm-console-proxy should be enabled by configuration API instead of feature falgs.

User Stories

As a cluster admin, I like to have a proper understanding, if the feature is considered as stable, or preview, so that I can be sure to use only stable features.

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

is duplicated by

CNV-42371 Move feature gate validation into the reconciliation loop

is related to

CNV-26552 GA: Manage Service Account for temporary VNC access

relates to

CNV-34216 Adjust downward metrics to KubeVirt Feature Lifecycle