failed to cause an issue by attempting to upgrade from version v.19.2.12 to v20.2.3 - unclear how to upgrade CRDB version

EXPECTED RESULT: when the cockroachDB version is specified to be an updated version from the current version of the DB, in the Openshift operator, it should upgrade or fail. There should be some kind of notification somewhere? Or some kind of indication of something happening.

ACTUAL RESULT: nothing happened and I don't know why. I changed the operator config and reloaded my containers and it seems to have had no impact.

In my write up this implies that there is something wrong with CRDB or with Openshift however it is completely possible that I had no idea what I was doing because there was no documentation on how to update the version of CRDB in this environment, updating the Operator config and reloading may have been the wrong step? Perhaps this needs someone with some expertise to write up some documentation on the specific steps to update the version..

detailed replication steps: [referring to this documentation https://www.cockroachlabs.com/docs/v21.1/deploy-cockroachdb-with-kubernetes-openshift.html]

- specify in the operator crdb version v19.2.12
- then change operator yaml to specify "v20.2.3" and then save and reload [expected to fail]
- nothing actually happened after save and reload, so I manually went into pods and deleted the operator pod and it created a new operator pod
- the existing CRDB pods were still using the previous version and did not self-delete, so I deleted one of the CRDB pods, and it created a new one. So now I have 2 pods using v19.2.12 and one pod running v20.2.3

➜ ~ oc get pods
NAME READY STATUS RESTARTS AGE
cockroach-operator-68977698f7-fcfxh 1/1 Running 0 119s
crdb-client-secure 1/1 Running 0 26m
crdb-tls-example-0 1/1 Running 0 30m
crdb-tls-example-1 1/1 Running 0 29m
crdb-tls-example-2 1/1 Running 0 57s
crdb-tls-example-vcheck-27021277-v78jq 0/1 Completed 0 30m

crdb-tls-example-2 is the one that *should* be running v20.2.3.. but I don't think it is.

- now I update my client secure pod (from step 4) - however that didn't work, so I deleted it and created a new one using my updated container image data from crdb-tls-example-2
- when I go into the pod and try the "cockroach version" command it still shows v19.2.12
- I tried deleting all of the pods and re-creating them, the pods still do not show v20.2.3 even though the operator is configured with "cockroachDBVersion": "v20.2.3",

Hope this is helpful