Grafana operator 5.16 change in .spec.Version

[ilabrovic]

In Grafana Operator 5.13, .spec.version in Grafana resource is filled with a version number automatically with a readable version number e.g.: .spec.version: 10.4.3
In Grafana Operator 5.16, we can see .spec.version automatically filled with a docker notation e.g.: .spec.version: docker.io/grafana/grafana@sha256:a0f881232a6fb71a0554a47d0fe2203b6888fe77f4cefb7ea62bed7eb54e13c3

Did something change in any Grafana Operator version between 5.13 and 5.16 that handles setting the key .spec.version?

As a followup, when i query "oc get grafana", only the old Grafanas still show a version number, but newer Grafanas not
$ oc get grafana --all-namespaces
NAMESPACE NAME VERSION STAGE STAGE STATUS AGE
ns-new-grafana grafana. complete success 42m. (<<< VERSION is missing in the display in new Grafanas)
ns-old-grafana. grafana 10.4.3 complete success 21d
This is because .status.version has not been set.
Did any change occur in Operator version in keeping .status.version as well?

[theSuess]

Version 5.16 fixes a bug regarding the handling of versions in openshift by allowing the version to be an image spec. This is relevant for OpenShift clusters (especially air-gapped ones) as the installation provides a specific image to use. This field is set by the operator on creation, if no value has been provided by the user. You can always overwrite this with a version (or image) of your choice

The spec.version field is used to tell the operator the desired version of the instance while the status.version is the current version as reported by Grafana. If this is not set correctly, this is a bug and should be fixed. Sometimes it might take a few minutes for this to be updated though.

[ilabrovic]

Status is working again.
It seemed our networkpolicy was not configured properly (wrong labelselector) so the operator could not reach the grafana service.
Good thing we have logging in the operator pods!
Thanks @theSuess !