Goal

The CNV operators alerts and recording rules code is currently embedded in the heart of the operators code.
This causes issues with code readability, code complexity and maintainability etc.
We would like to

• 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

  User Stories

• High-Level goal-based user story, with context.
• As a core CNV Developer I want be able to have a readable code, that is not cluttered with monitoring code and is easier to maintain.
• As a CNV monitoring developer I would like to have the metrics and all of the monitoring code and logic in a separate place where it will be easier to read and maintain.
  As part of CNV-21957 it will be decided on how to refactor the code so it will:

• As a user I would like to be able to opt-in and opt-out of specific metrics types.

Non-Requirements

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

Notes

• we are mainly focusing on kubevirt/kubevirt (we will eventually extend it to other operators later on), it's just about code refactoring, no impact on existing tier2 (and maybe also tier1) tests.
• at the first step we think only about refactoring the code but continue executing it in the same pod where is now. We can think later on to move it to a different container or even different pod.

Done Checklist