Skip to content

RELEASE.md

Latest commit

 

History

History
31 lines (24 loc) · 2.1 KB

RELEASE.md

File metadata and controls

31 lines (24 loc) · 2.1 KB
Raw

Release instructions

Steps to release a new version of the Tempo Operator:

  1. Checkout the main branch, and make sure you have the latest changes.
  2. Confirm that MIN_KUBERNETES_VERSION and MIN_OPENSHIFT_VERSION in the Makefile are still up-to-date, and create a PR if required.
  3. Go to GitHub Actions Tab, In the left sidebar, choose "Prepare Release" Workflow, then push in the "Run workflow" button , select the main branch and type the version of operator to release
  4. Push "Run workflow", this will trigger the process to generate the CHANGELOG and generate the bundle, this will create a PR with the title "Prepare Release vx.y.z`"
  5. Once the PR is created, use that branch to build, deploy and, run OpenShift tests against an OpenShift cluster (see below for instructions).
  6. Once the PR above are merged and available in the main branch, it will trigger the release workflow which will create the tag and the GitHub release.

Running e2e tests on OpenShift

A locally installed CRC cluster can be used for testing.

Note: The e2e tests require opentelemetry-operator and cluster monitoring operator (crc config set enable-cluster-monitoring true).

kubectl create namespace openshift-tempo-operator
IMG_PREFIX=docker.io/your_username OPERATOR_VERSION=x.y.z BUNDLE_VARIANT=openshift OPERATOR_NAMESPACE=openshift-tempo-operator make build docker-build docker-push bundle bundle-build bundle-push olm-deploy
make e2e e2e-openshift

Release Schedule

We plan to release the operator monthly, at the end of each month.

Version Release Manager
0.19.0 Ruben Vargas
0.20.0 Pavol Loffay
0.21.0 Benedikt Bongartz
0.22.0 Andreas Gerstmayr