-
Sub-task
-
Resolution: Done
-
Undefined
-
None
-
None
Bump upstream sail operator patch version. e.g. https://github.com/istio-ecosystem/sail-operator/pull/863
When releasing multiple ossm version, you have to do it for all of them
Tasks:
- Clone https://github.com/istio-ecosystem/sail-operator/ repo
- Checkout to desired branch,
- change Makefile.core.mk:
- Bump version in VERSION env
- Run make gen (or BUILD_WITH_CONTAINER=0 make gen)
- Commit, Push, ask for Review, Merge
Example of PRs:
bump 1.0.3 -> 1.0.4
Bump up patch version of operator in the release branch for downstream repos. (to next patch release) and add released images there
Tasks:
- Clone https://github.com/openshift-service-mesh/sail-operator/ repo
- Checkout to desired branch,
- change Makefile.vendor.mk:
- Bump version in VERSION env
- change ossm/values.yaml:
- Change version and replacesVersion there
- Change ENV_VARIABLES (e.g. `images.v1_26_2.cni: ${ISTIO_CNI_1_26}` to `images.v1_26_2.cni: registry.redhat.io/...` ) to released images with shas
- You can find the shas in konflux in snapshot for that release (or directly in the RH catalog)
- Try to pull all new images locally to be sure that URL's are correct in values.yaml
- e.g. PR https://github.com/openshift-service-mesh/sail-operator/pull/447/files where only images are changed (but you don't need to create separate PR for images only)
- Run make gen (or BUILD_WITH_CONTAINER=0 make gen)
- Commit, Push, ask for Review, Merge
Example of PRs:
bump 3.0.0 -> 3.0.1
bump 3.0.2 -> 3.0.3
bump 3.0.3 -> 3.0.4
- clones
-
-
- Backlog
-