Update OpenShift templates

[tolusha]

Signed-off-by: Anatolii Bazko abazko@redhat.com

What does this PR do?

Update OpenShift templates.

Regarding codeready labels.
We should be consistent with those created by operator. It uses cheFavor field from the CR to set labels.

What issues does this PR fix or reference?

https://issues.redhat.com/browse/RHDEVDOCS-2483

[tolusha]

Regarding hardcoded 2.7 tag
I assume update_template.sh script should be a part of some sync procedure.
For now I run it manually to update templates.

[nickboldt]

For now I run it manually to update templates.

What template file do you pass to the script? does it only have "nightly" as image tag version?

As to sync process, there is no such thing today as registries are forks from upstream. Introducing a new manual process is bad.

Instead, you could call your new script in one of two ways:

• every time a CI build fires - https://gitlab.cee.redhat.com/codeready-workspaces/crw-jenkins/-/tree/master/jobs/CRW_CI (find devfile and plugin reg jobs for 2.7 and 2 branches in there) - probably overkill, but it's an option

• every time we start a new branch (every 6 weeks) - https://gitlab.cee.redhat.com/codeready-workspaces/crw-jenkins/-/blob/master/jobs/CRW_CI/Releng/update-version-and-registry-tags.jenkinsfile#L27 -> https://github.com/redhat-developer/codeready-workspaces/blob/crw-2-rhel-8/product/updateVersionAndRegistryTags.sh#L63-L101 - this is a better option, as we only have to bump from 2.7 -> 2.8 once per release.

[tolusha]

I will update Jenkins file soon.

[tolusha]

@nickboldt
I hope I addressed all your remarks.
Once PR is approved I will create a MR to update Jenkins file

[nickboldt]

Merged and cherrypicked.

See followup in #434