Prerequisite:
Do this steps only AFTER `Create Kiali upstream releases` and `Update RPMs in Konflux` tasks are finished.` tasks are finished.

Tasks: (must be done sequentially)

1. Make sure that gitmodules in ossm(https://gitlab.cee.redhat.com/istio/konflux/ossm), kiali(https://gitlab.cee.redhat.com/istio/konflux/kiali) and istictl(https://gitlab.cee.redhat.com/istio/konflux/istioctl) konflux repos points to the latest/desired/correct commits for each release branch. (commits which are the latest ones in release branches)
   1. e.g. (for 3.0.3, gitmodules points to istio commit '0fdb6a7e' which should be the latest one in release-3.0 branch that time, so that is correct, we need to check for all gitmodules)
   2. you can use `make validate-git-modules` script in each branches
2. Make sure that all desired PRs are merged in konflux and product repositories for release branches
3. Make sure, that all bundle patch scripts for the older versions in all new versions branches are in sync with the same script in the older branch
   1. e.g. latest 3.0 images are in ossm-3.0 branch here: https://gitlab.cee.redhat.com/istio/konflux/ossm/-/blob/ossm-3.0/bundle-patch/export-images-v3-0.sh?ref_type=heads  (konflux automatically updates that script )
   2. but also ossm-3.1 (and next ones) must have updated those images in their branches, https://gitlab.cee.redhat.com/istio/konflux/ossm/-/blob/ossm-3.1/bundle-patch/export-images-v3-0.sh?ref_type=heads  (konflux doesn't automatically update that), so right before code freeze, update
4. Set the code freeze in Konflux.
   1. Update `renovate.json` in ossm, kiali, ossm-fbc, kiali-fbc and istioctl konflux repos with `"automerge": false`
   2. e.g.:
      1. https://gitlab.cee.redhat.com/istio/konflux/kiali/-/merge_requests/462
      2. https://gitlab.cee.redhat.com/istio/konflux/ossm/-/merge_requests/387
      3. https://gitlab.cee.redhat.com/istio/konflux/ossm-fbc/-/merge_requests/48 
      4. https://gitlab.cee.redhat.com/istio/konflux/kiali-fbc/-/merge_requests/59
      5. https://gitlab.cee.redhat.com/istio/konflux/istioctl/-/merge_requests/56 
   3. !!! After this, the PRs for updating gitmodules will be still created automatically but not auto-merged. Since the PR can contain a change not related to the release but also a change with hotfix for a release, it is up to the release coordinator to merge it manually or not. !!! (only hot-fixes for release should be merged manually after code freeze)
5. Wait will all `...on-push...` builds are done for a particular kiali/ossm version. And after that, wait ~5 hours ( in case some on push build just finished, we want from automation to create `nudge` PR for updating bundle ). You don't need to wait 5hours, but after code freeze of nudge, you need to do not forget to merge the PR manually.
6. Set the code freeze in Konflux for nudge.
   1. Update `tenants-config/cluster/stone-prod-p02/tenants/service-mesh-tenant/nudging-config.yaml` in https://gitlab.cee.redhat.com/releng/konflux-release-data with `"automerge": false`
   2. Run `/tenants-config/build-single.sh service-mesh` to regenerate config and create PR
   3. e.g.: https://gitlab.cee.redhat.com/releng/konflux-release-data/-/merge_requests/7153 
   4. !!! After this, the PR for updating image references in the bundle still will be created (when some change in containers/operands will be merged) but not automerged so the release coordinator should take this into account when manually merging PR for containers after code freeze !!!