-
Task
-
Resolution: Done
-
Undefined
-
None
-
None
Tasks: (Note: keep note that releasing all things and verifying that everything works can take ~3 hours, so do not start close to the end of the working day)
- As part of task `(At ReleaseCandidate): Prepare release resources and add there CVEs`, the Release PRs should already exist. Verify, that all snapshots values are the latest ones and match with test matrix document
- Ask someone for a final review and merge the PRs
- Once, it will be merged, apply those CRs in the Konflux cluster
- Login to konflux cluster (`oc login https://api.stone-prod-p02.hjvn.p1.openshiftapps.com:6443/ --web`)
- Change project to `service-mesh-tenant`
- 1st, apply Release CR for the previous releases for Kiali (because, bundle in the current release needs to have containers from the previous release already in prod)
- Apply previous version containers Kiali Release CR
- e.g. for 3.0.3 release, (which contained kiali 1.73 for ossm 2.4.6 release), checkout to the `ossm-2.6` branch in kiali konflux and apply merged Release CR `oc apply -f releases/ossm-3.0.3/kiali-2.4.6.yaml`
- Once it is applied, go to the Konflux UI -> application (kiali-2-6 for this) -> Releases tab and you will see the new release to prod there with In Progress status. (you can follow the progress in managed pipeline)
- Wait, till release status is Succeeded
- Now, the containers are in the production, you can verify that in the RedHat catalog https://catalog.redhat.com/search?searchType=containers
- Apply previous version containers Kiali Release CR
- 2nd, apply Release CRs for the current release of Kiali and OSSM
- Apply Kiali and OSSM Release CRs (this can be done in parallel)
- e.g. for 3.0.3 release, checkout to the `ossm-3.0` branch in kiali konflux repo and apply merged Release CR `oc apply -f releases/ossm-3.0.3/kiali-2.4.6.yaml`
- e.g. for 3.0.3 release, checkout to the `ossm-3.0` branch in ossm konflux repo and apply merged Release CR `oc apply -f releases/ossm-3.0.3/ossm-3.0.3.yaml`
- Once it is applied, go to the Konflux UI -> application (ossm-3.0 or kiali-3.0 for release above) -> Releases tab and you will see the new release to prod there with In Progress status. (you can follow the progress in managed pipeline)
- Wait, till release status is Succeeded
- Now, the containers are in the production, you can verify that in the RedHat catalog https://catalog.redhat.com/search?searchType=containers
- Apply Kiali and OSSM Release CRs (this can be done in parallel)
- Once, all containers are in production registry, we can continue with applying FBC Releases
- Apply all FBC Release CR's
- e.g. for 3.0.3 release, checkout to the `ossm-3.0` branch in kiali and ossm konflux repo and apply all FBC's Release CRs in `releases/ossm-3.0.3/fbc`
- Once it is applied, go to the Konflux UI -> application (select all FBCs which you released) -> Releases tab and you will see the new release to prod there with In Progress status. (you can follow the progress in managed pipeline)
- Wait, till release status is Succeeded
- Now, the containers are in the production, you can verify that in the RedHat catalog https://catalog.redhat.com/search?searchType=containers
- Now, the FBCs should be in production registry
- Apply all FBC Release CR's
- After that, all images will be in prod registry and shipped live
- Right after that, continue with `(At Release) Cursory Check After Release is Shipped Live` task to check that all images are correct and clusters are able to install it
- clones
-
OSSM-9251 Push to production tasks
-
- Backlog
-