Create new patch release (Z-release) entries in Konflux. Do this task only after unfreezing Konflux, since we need newer builds in Quay repository for the next version.

OSSM fbc

• You have to change https://gitlab.cee.redhat.com/istio/konflux/ossm-fbc/-/blob/main/catalog/catalog-template.yaml?ref_type=heads (use the branch for the current stream, e.g. ossm-3.0 for 3.0.z patches) with next patch version
  • Add new version in channels entries ( update name, replaces and skipRange)
  • Add released bundle ( you can find the released version in RH catalog https://catalog.redhat.com/software/containers/openshift-service-mesh/istio-sail-operator-bundle/67ab6f5f9e87ae6cc720911a?gs&q=service%20mesh%20operator )
  • Update Quay bundle there with the latest bundle from Konflux (Konflux > Application > OSSM x.y > Releases , latest release to stage > Snapshot > copy bundle sha and update in bundle template )
• Make sure, you are logged in to the konflux cluster ( `oc login https://api.stone-prod-p02.hjvn.p1.openshiftapps.com:6443/ --web` ) or set `REGISTRY_USER` and `REGISTRY_PASSWORD` envs with credentials to registry.redhat.io 
• Execute command `make generate-fbc-catalog` to generate the FBC catalogs.
• Create PR with changes
  • example of PRs after 3.0.3 release (ignore tmp change in fbc-next): https://gitlab.cee.redhat.com/istio/konflux/ossm-fbc/-/merge_requests/52 

Kiali (ignore when a newer minor version of OSSM exists.  (Kiali operator is updated only for the latest minor OSSM version) e.g., whenthe  kiali operator is in OSSM 3.1, there is no newer kiali operator anymore in the OSSM 3.0 stream)

• FBC
  • Ask someone from Kiali team to bump up operator version in upstream
    • Bump to the next patch version in the kiali-operator repo 
      • e.g. after ossm 3.0.3 release (kiali 2.4.6)  kiali-operator: https://github.com/kiali/kiali-operator/pull/932 
    • Create a tag with the next version as next release candidate in all repos
      • e.g. 2.4.7-rc after 2.4.6 ga
  • Wait till konflux update gitmodules to point to the latest commit ( or update gitmaodules in konflux manually)
  • After PR is merged, wait until the operator build finished (it takes ~27 minutes, Konflux > Application > Kiali X.Y > component > operator), then wait for release to stage.
  • You have to change https://gitlab.cee.redhat.com/istio/konflux/kiali-fbc/-/blob/main/catalog/ossm-3-0/catalog-template.yaml?ref_type=heads (use the branch for the current stream, e.g. ossm-3.0 for 3.0.z patches)  with next patch version
    • Add new version in channels entries ( name and replaces)
    • Add released bundle ( you can find the released version in RH catalog https://catalog.redhat.com/software/containers/openshift-service-mesh/kiali-operator-bundle/6523f98ba089673f821825b6?gs= )
    • Update Quay bundle there with the latest bundle from Konflux (Konflux > Application > Kiali x.y > Releases , latest release to stage > Snapshot > copy bundle sha and update in bundle template ) (That should be the build that you have run manually in the task above)
  • Make sure, you are logged in to the konflux cluster ( `oc login https://api.stone-prod-p02.hjvn.p1.openshiftapps.com:6443/ --web` ) or set `REGISTRY_USER` and `REGISTRY_PASSWORD` envs with credentials to registry.redhat.io 
  • Execute command `make generate-fbc-catalog` to generate the FBC catalogs.
  • Create PR with changes
    • example of PRs after 3.0.3 release: https://gitlab.cee.redhat.com/istio/konflux/kiali-fbc/-/merge_requests/65 
• Bundle
  • You have to bump KIALI_OLD_OPERATOR_VERSION and KIALI_METADATA_VERSION  https://gitlab.cee.redhat.com/istio/konflux/kiali/-/blob/ossm-3.0/bundle.Containerfile?ref_type=heads (use the branch for the current stream, e.g. ossm-3.0 for 3.0.z patches) 
  • Create PR with changes
    • example of PRs after 3.0.3 release: https://gitlab.cee.redhat.com/istio/konflux/kiali/-/merge_requests/541