- Get the
OAUTH_TOKEN
from Github, selectrepo:status
scope. - Run
OAUTH_TOKEN=... make changelog
- Remove the commits that are not relevant to users, like:
- CI or testing-specific commits (e2e, unit test, ...)
- bug fixes for problems that are not part of a release yet
- version bumps for internal dependencies
Steps to release a new version of the Jaeger Operator:
-
Change the
versions.txt
so that it lists the target version of the Jaeger (if it is required). Don't touch the operator version: it will be changed automatically in the next step. -
Confirm that
MIN_KUBERNETES_VERSION
andMIN_OPENSHIFT_VERSION
in theMakefile
are still up-to-date, and update them if required. -
Run
OPERATOR_VERSION=1.30.0 make prepare-release
, using the operator version that will be released. -
Run the E2E tests in OpenShift as described in the CONTRIBUTING.md file. The tests will be executed automatically in Kubernetes by the GitHub Actions CI later.
-
Prepare a changelog since last release.
-
Update the release manager schedule.
-
Commit the changes and create a pull request:
git commit -sm "Preparing release v1.30.0"
-
Once the changes above are merged and available in
main
tag it with the desired version, prefixed withv
, eg.v1.30.0
git checkout main git tag v1.30.0 git push git@github.com:jaegertracing/jaeger-operator.git v1.30.0
-
The GitHub Workflow will take it from here, creating a GitHub release and publishing the images
-
After the release, PRs needs to be created against the Operator Hub Community Operators repositories:
- One for the upstream-community-operators, used by OLM on Kubernetes.
- One for the community-operators used by OpenShift.
This can be done with the following steps:
- Update main
git pull git@github.com:jaegertracing/jaeger-operator.git main
- Clone both repositories
upstream-community-operators
andcommunity-operators
- Run
make operatorhub
- If you have
gh
installed and configured, it will open the necessary PRs for you automatically. - If you don't have it, the branches will be pushed to
origin
and you should be able to open the PR from there
- If you have
After the PRs have been made it must be ensured that:
- Images listed in the ClusterServiceVersion (CSV) have a versions tag #1682
- No
bundle
folder is included in the release - No foreign CRs like prometheus are in the manifests
The operator should be released within a week after the Jaeger release.
Version | Release Manager |
---|---|
1.58.0 | Benedikt Bongartz |
1.59.0 | Pavol Loffay |
1.60.0 | Israel Blancas |
1.61.0 | Ruben Vargas |