Release Guide

MacOS users

Install GNU sed and make which may not be by default:

We will use the v1.3.0 release version in this example.

  1. A release branch must be created and mapped before the release begins to appease the Netlify website configuration demons. You can ping SDK to ensure a release branch is created prior to the release and that this mapping is created. If you have the proper permissions, you can do this by running the following, assuming the upstream SDK is the upstream remote repo:
  1. git checkout master
  2. git pull
  3. git checkout -b v1.3.x
  4. git push -u upstream v1.3.x
  1. Create and merge a commit that updates the top-level variable IMAGE_VERSION to the upcoming release tag v1.3.0. This variable ensures sample projects have been tagged correctly prior to the release commit.
  1. sed -i -E 's/(IMAGE_VERSION = ).+/\1v1\.3\.0/g' Makefile
  1. Lock down the master branch to prevent further commits before the release completes:
  2. Go to Settings -> Branches in the SDK repo.
  3. Under Branch protection rules, click Edit on the master branch rule.
  4. In section Protect matching branches of the Rule settings box, increase the number of required approving reviewers to 6.

1. Create and push a release commit

Create a new branch to push the release commit:

  1. git checkout master
  2. git pull
  3. git checkout -b release-v1.3.0

Run the pre-release make target:

The following changes should be present:

  • changelog/generated/v1.3.0.md: commit changes (created by changelog generation).
  • changelog/fragments/*: commit deleted fragment files (deleted by changelog generation).
  • website/content/en/docs/upgrading-sdk-version/v1.3.0.md: commit changes (created by changelog generation).
  • website/config.toml: commit changes (modified by release script).

Commit these changes and push:

2. Create and merge a new PR

Create and merge a new PR for the commit created in step 1. You can force-merge your PR to the locked-down master if you have admin access to the operator-sdk repo, or ask an administrator to do so.

3. Unlock the master branch

4. Create and push a release tag

  1. make tag RELEASE_VERSION=v1.3.0
  2. git push upstream v1.3.0

The latest branch points to the latest release tag to keep the main website subdomain up-to-date. Run the following commands to do so:

  1. git checkout latest
  2. git reset --hard tags/v1.3.0

Similarly, to update the release branch, run:

  1. git checkout v1.3.x
  2. git reset --hard tags/v1.3.0
  3. git push -f upstream v1.3.x

6. Post release steps

  • Make an post.
  • Post to Kubernetes slack in #kubernetes-operators and #operator-sdk-dev.
  • In the GitHub milestone, bump any open issues to the following release.

We will use the v1.3.1 release version in this example.

Before starting

  1. Create and merge a commit that updates the top-level Makefile variable IMAGE_VERSION to the upcoming release tag v1.3.1. This variable ensures sample projects have been tagged correctly prior to the release commit.
  1. sed -i -E 's/(IMAGE_VERSION = ).+/\1v1\.3\.1/g' Makefile
  1. Lock down the v1.3.x branch to prevent further commits before the release completes:
  2. Go to Settings -> Branches in the SDK repo.
  3. Under Branch protection rules, click Edit on the branch rule.
  4. In section Protect matching branches of the Rule settings box, increase the number of required approving reviewers to 6.

1. Create and push a release commit

Create a new branch from the release branch, which should already exist for the desired minor version, to push the release commit to:

Run the pre-release make target:

  1. make prerelease RELEASE_VERSION=v1.3.1

The following changes should be present:

  • changelog/generated/v1.3.0.md: commit changes (created by changelog generation).
  • changelog/fragments/*: commit deleted fragment files (deleted by changelog generation).

Commit these changes and push:

  1. git add --all
  2. git commit -m "Release v1.3.1"
  3. git push -u origin release-v1.3.1

2. Create and merge a new PR

Unlock the branch by changing the number of required approving reviewers in the v.* branch rule back to 1.

4. Create and push a release tag

  1. make tag RELEASE_VERSION=v1.3.1
  2. git push upstream v1.3.1

5. Fast-forward the latest branch

The latest branch points to the latest release tag to keep the main website subdomain up-to-date. Run the following commands to do so:

  1. git checkout latest
  2. git reset --hard tags/v1.3.1
  3. git push -f upstream latest

6. Post release steps

Binaries and signatures

Binaries will be signed using our CI system’s GPG key. Both binary and signature will be uploaded to the release.

Each minor release has a corresponding release branch of the form vX.Y.x, where X and Y are the major and minor release version numbers and the x is literal. This branch accepts bug fixes according to our .

Cherry-picking

Once a minor release is complete, bug fixes can be merged into the release branch for the next patch release. Fixes can be added automatically by posting a /cherry-pick v1.3.x comment in the master PR, or manually by running:

Create and merge a PR from your branch to .

GitHub release information

GitHub releases live under the Releases tab in the operator-sdk repo.