This task is related only Minor release (Y release). Ignore during patch release (Z release) since the newer version should be already created as part of postGA task in previous release.

WIP update according to work for OSSM 3.1

• Creation of release branches for downstream repos
  • Create release-3.x branch in openshift-service-mesh/sail-operator repo. Use the respective upstream release branch as a base
  • Create CI jobs for the new branch in openshift-release repo
  • Create a PR that copies the latest OSSM-specific changes from the main branch. You can do this quickly by running the following: git checkout main Makefile.vendor.mk && git checkout main docs/ossm && git checkout main ossm && make gen
  • Make sure that latest istio patch version is used ( e.g. for OSSM 3.0, we have istio 1.24.z ), if not, ask on the team slack channel about an upgrade in upstream sail operator, midstream istio and proxy)
• Creation of new branch in Konflux repo
• Creation of Konflux components
• Adapt tekton pipelines and git submodules
• New bundle patch images file
• New channel in the FBC
• Add pull secrets of private repos to Konflux service accounts (proxy, bundle and FBCs) - https://console-openshift-console.apps.stone-prod-p02.hjvn.p1.openshiftapps.com/k8s/ns/service-mesh-tenant/serviceaccounts
• When creating a new minor release for Konflux, a new entry will have to be created for it in Product Definitions.
  • Update https://gitlab.cee.redhat.com/prodsec/product-definitions/-/blob/master/data/openshift/ps_modules.json and https://gitlab.cee.redhat.com/prodsec/product-definitions/-/blob/master/data/openshift/ps_update_streams.json with new minor version (see existing version structure)

QUESTION, TBD:

• will must-gather have separated release branch?

Links:

• OSSM 3.x release process doc - Downstream release - Branch preparation