-
Epic
-
Resolution: Done
-
Major
-
None
-
kubevirt-monitoring-tests-4.16
-
-
Green
-
To Do
-
CNV-8094 - CNV Observability
-
0% To Do, 0% In Progress, 100% Done
-
dev-ready, doc-ready, po-ready, qe-ready, ux-ready
-
Goal
This epic is about adding additional tests related to monitoring.
1. The KubeVirt metrics code is currently embedded in the heart of the operator code.
This causes issues with code readability, code complexity and maintainability etc.
We worked to separate the code so that it will:
- Enhance development speed
- Decouple the monitoring code from operator code
- Enhance security: monitor publicly available data only
- Become more modular and generic - resilient to future changes.
We want to add a test to all operators to make sure the code separations is kept.
2. Add a test that will limit the length of an alerts, since it is too long it does not fit on the TOC of the docs.
User Stories
- As a core KubeVirt Developer I want to catch early if I added a monitoring code in incorrect place.
- As a core KubeVirt Developer I want to catch early if I named an alert with a name that is too long that can cause issues.
Non-Requirements
- List of things not included in this epic, to alleviate any doubt raised during the grooming process.
Notes
Done Checklist
| Who | What | Reference |
|---|---|---|
| DEV | Upstream roadmap issue (or individual upstream PRs) | <link to GitHub Issue> |
| DEV | Upstream documentation merged | <link to meaningful PR> |
| DEV | gap doc updated | <name sheet and cell> |
| DEV | Upgrade consideration | <link to upgrade-related test or design doc> |
| DEV | CEE/PX summary presentation | label epic with cee-training and add a <link to your support-facing preso> |
| QE | Test plans in Polarion | <link or reference to Polarion> |
| QE | Automated tests merged | <link or reference to automated tests> |
| DOC | Downstream documentation merged | <link to meaningful PR> |
