spec.Image field always overwritten by Operand image for CVE releases

[ryanemerson]

If a user provides a customer image via spec.image, then the StatefulSet is initially provisioned with the specified image. However, the Operator then determines that the provisioned image is not the same as the image associated with spec.version and initialises a rolling upgrade of the StatefulSet resulting in the Operand image value always being used.

statefulset_updates.go needs to be updated to not initiate a rolling upgrade if the container image matches the one provided by spec.image.

This only occurs if the configured spec.version relates to an Operand that is marked as a CVE release.

Workaround

As a custom image is being used, it's possible to update the spec.version to an Operand that is not marked as a CVE release.