Description

As a WMCO user, I want necessary resources to be operator managed so that accidental resource changes/deletions don't require manual intervention.

This story covers making WMCO manage the windows-exporter ServiceMonitor and Service resources that are part of the bundle manifests. WMCO should watch these such that any destructive user changes are kicked back, whether that is metadata/spec edits or resource deletion.

Acceptance Criteria

• WMCO reacts to deletion of windows-exporter ServiceMonitor and Service by properly re-creating the resources
• WMCO reacts to user edits to the windows-exporter ServiceMonitor and Service yamls by reverting them