-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
cnv-downward-lifecyle
-
- downward metrics are enabled and disabled via a config setting, nut not via a feature gate
- the documentation is adjusted
- qe tests are adjusted
-
Red
-
CNV-38613 - 2024 Code Quality
-
CNV-386132024 Code Quality
-
53% To Do, 13% In Progress, 33% Done
-
dev-ready, doc-ready, po-ready, qe-ready, ux-ready
-
-
Yes
Goal
Currently, the downward metrics feature is behind the feature gate `downwardMetrics`. This feature is already GA. Therefore, the feature gate has to be removed according to https://github.com/kubevirt/community/blob/main/design-proposals/feature-lifecycle.md#feature-stages. However, the feature needs to have the flexibility to be disabled at any time.
User Stories
As Cluster Admin, I want to get rid of the downward metrics feature gate while having the flexibility to enable or disable the downward metrics feature.
As Cluster Admin, I want to have gross and granular access control options for this feature so it will fit any environment restrictions.
Non-Requirements
- No feature gate anymore
Notes
- Requires to deprecate the FG and enabling the new spec KubeVirt first before deprecating the FG and implementing the spec enablement in HCO.
- is documented by
-
CNV-43925 Update downstream documentation
- New
- is duplicated by
-
CNV-42371 Move feature gate validation into the reconciliation loop
- New
- is related to
-
CNV-40958 All new features should have granular access control
- New
-
CNV-34204 Adjust vm-console-proxy to KubeVirt Feature Lifecycle
- Closed
-
CNV-40231 HostName should not be displayed in the downwardMetrics
- POST
-
CNV-47366 Update downstream documentation
- Closed
- relates to
-
CNV-46505 Network: mature or remove old feature flags
- New
-
CNV-46516 Storage: mature or remove old feature flags
- New
-
CNV-46525 Compute: mature or remove old feature gates
- New