Old identityProvider and postgres container images not updated to latest defaults on Operator update.

[davidfestal]

When the Che operator is updated (for example from beta-5.0 to rc-2.0), and a Che server CR was previously started with the default Keycloak docker image (empty string), the Che server is not upgraded with the new default keycloak image after operator upgrade, but stays on the effective Keycloak version that was initially deployed.

[nickboldt]

We've seen this in downstream CRW 1.2 too. And it's not just the identity provider (Keycloak/SSO) image but also the postgres db that remains on the image:tag of the initial deployment.

WORKAROUND is to patch the deployment, as we do here:

https://github.com/redhat-developer/codeready-workspaces-deprecated/blob/6.19.x/operator-installer/migrate_1.1_to_1.2.sh#L280-L306

But a better solution would be ... um, better. :)

[ibuziuk]

@davidfestal can we close this one ?

[davidfestal]

I assume yes, even though it is not in production of course.

[ibuziuk]

Fixed in eclipse-che/che-operator#72 and operator nightly builds