Currently, each component of the MCO has its own metric registering function in pkg/operator/metrics.go, pkg/controller/metrics.go, pkg/daemon/metrics.go, which resulted in duplication. This also adds difficulty for future CRD works. As a result, there is a strong call for a centralized metric spinning up mechanism, which takes whatever metric passed in and register for those, in the state controller. 

Completion criteria

1. Should be able to turn on/off all the metrics from one centralized place, without any touch on MCC, MCD or MCO
2. Should be able to only register for the metrics according to user's choices

Update:

• Blocked by state controller design change
• Design completed in spike MCO-134, linked below. Design doc can be found in: https://docs.google.com/document/d/1jAoHAAkSfX9VQVAOd0plXoR1J0FMKmXjzqA6F-fDKng/edit