Description of problem:

In the demo env, since migrating to 2.12, the observability addon status of spoke `sno-vm2` is flapping between `Progressing` and `Available`.

The root cause is that the endpoint collector does not check wether the deployment of the collector was updated before setting the status to Progressing.

Also this is especially visible for this spoke because:

• Multiple reconciles are being triggered by openshift-monitoring/cluster-monitoring-config while only the metadata.managedFields[0].time changed. It changes constantly.
• The collector has some errors when forwarding the metrics with 409, leading to a delay for setting the status to Available

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

1.  
2.  
3. ...

Actual results:

Expected results:

Additional info: