At least if a new image is available for UPS (and oauth-proxy and postgresql?), then deployments should get updated I guess.

That would mean auto update ...which I don't think is in the scope.

The versions of components installed by the operator are hardcoded: https://github.com/aerogear/unifiedpush-operator/blob/1aebbf930d554cb2a18f582acfeabee5e74a3d19/pkg/controller/unifiedpushserver/util.go#L30

I saw similar pattern in Keycloak operator for example: https://github.com/integr8ly/keycloak-operator/blob/27e896b480e7d65d86f34fc62c7c6ea11832a687/pkg/keycloak/keycloak.go#L30

Anyway, the way I would see this task is:

• A version of the operator is bound to a version of UPS
• UPS operator should check if the version of existing UPS is the expected one. If it is below, update the deployment for UPS. Same goes on with the other managed components like Oauth proxy and Postgres
• ...

Wei Li Sounds good?

I looked and asked around a little bit and wasn't able to find a task similar to this one at AeroGear/RHMI.