During upgrade of a cluster in CI build farm, we have seen a sequence of alerts and messages of failures from clusterversion.

From: 4.3.17
To: 4.4.0-rc.12

Eventually upgrade was completed successfully (which is so nice).
But those alerts and messages are too frightening.

I would like to create a bug for each of those and feel better for the next upgrade.

https://coreos.slack.com/archives/CHY2E1BL4/p1588025768126900

[FIRING:1] ImagePruningDisabled image-registry-operator (60000 10.128.0.53:60000 openshift-image-registry cluster-image-registry-operator-6c6cc5b9c8-rjgdb openshift-monitoring/k8s image-registry-operator warning)
Automatic image pruning is not enabled. Regular pruning of images
no longer referenced by ImageStreams is strongly recommended to
ensure your cluster remains healthy.
To remove this warning, install the image pruner by creating an
imagepruner.imageregistry.operator.openshift.io resource with the
name cluster. Ensure that the suspend field is set to false.

oc --context build01 get imagepruner.imageregistry.operator.openshift.io
NAME      AGE
cluster   41m

It is not using the default value false and fired an alert on this.

Would it make more sense to use the default value when creating it without triggering the alert?