XML

Word

Printable

Type: Epic
Resolution: Unresolved
Priority: Normal
Fix Version/s: CNV v4.18.0
Affects Version/s: None
Component/s: CNV Infrastructure
Labels:
- 418
- cnv4_18_scopeLock
- no-ui
- no-ux

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
Feature Link:
CNV-38613 - 2024 Code Quality
Parent Link:
CNV-386132024 Code Quality
Hierarchy Progress Bar:

29% To Do, 14% In Progress, 57% Done
Ready-Ready:

dev-ready, doc-ready, po-ready, qe-ready, ux-ready
Product Documentation Required:
Yes
Target Version:

CNV v4.18.0

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

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.

Non-Requirements

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

Notes

Any additional details or decisions made/needed

is related to

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

Closed

relates to

CNV-34216 Adjust downward metrics to KubeVirt Feature Lifecycle

In Progress

Assignee:: Andrej Krejcir

Reporter:: unassigned (Inactive)

QA Contact:: Geetika Kapoor

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2023/10/20 1:01 PM

Updated:: 2024/09/10 1:59 PM