kubernetes
/
minikube
mirror of https://github.com/kubernetes/minikube.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
minikube/docs/contributors/releasing_minikube.md

4.6 KiB
Raw Blame History

Steps to Release Minikube

Build a new ISO

You only need to build the minikube ISO when the there are changes in the deploy/iso folder. Note: you can build the ISO using the hack/jenkins/build_iso.sh script locally.

  • navigate to the minikube ISO jenkins job
  • Ensure that you are logged in (top right)
  • Click "▶️ Build with Parameters" (left)
  • For ISO_VERSION, type in the intended release version (same as the minikube binary's version)
  • For ISO_BUCKET, type in minikube/iso
  • Click Build

The build will take roughly 50 minutes.

Update Makefile

Edit the minikube Makefile, updating the version number values at the top:

  • VERSION_MINOR (and VERSION_MAJOR, VERSION_BUILD as necessary)
  • ISO_VERSION (only update this if there is a new ISO release - though there almost always is)

Run Local Integration Test

Once the ISO build completes, run run the integration tests with the updated Makefile:

env TEST_ARGS="-minikube-start-args=--vm-driver=kvm2" make integration

Ad-Hoc testing of other platforms

If there are supported platforms which do not have functioning Jenkins workers (Windows), you may use the following to build a sanity check:

env BUILD_IN_DOCKER=y make cross checksum

Send out Makefile PR

Once submitted, HEAD will use the new ISO. Please pay attention to test failures, as this is our integration test across platforms. If there are known acceptable failures, please add a PR comment linking to the appropriate issue.

Update Release Notes

Run the following script to update the release notes:

hack/release_notes.sh

Merge the output into CHANGELOG.md. See PR#3175 as an example. Then get the PR submitted.

Tag the Release

NOTE: Confirm that all release-related PR's have been submitted before doing this step.

Do this in a direct clone of the upstream kubernetes/minikube repository (not your fork!):

git fetch \
  && git checkout master \
  && git pull \
  && git tag -a v<version> -m "<version> Release" \
  && git push origin v<version>

Build the Release

This step uses the git tag to publish new binaries to GCS and create a github release:

  • navigate to the minikube "Release" jenkins job
  • Ensure that you are logged in (top right)
  • Click "▶️ Build with Parameters" (left)
  • VERSION_MAJOR, VERSION_MINOR, and VERSION_BUILD should reflect the values in your Makefile
  • For ISO_SHA256, run: gsutil cat gs://minikube/iso/minikube-v<version>.iso.sha256
  • Click Build

Check releases.json

This file is used for auto-update notifications, but is not active until releases.json is copied to GCS.

minikube-bot will send out a PR to update the release checksums at the top of deploy/minikube/releases.json. You should merge this PR.

Package managers which include minikube

These are downstream packages that are being maintained by others and how to upgrade them to make sure they have the latest versions

Package Manager URL TODO
Arch Linux AUR https://aur.archlinux.org/packages/minikube/ "Flag as package out-of-date"
Brew Cask https://github.com/Homebrew/homebrew-cask/blob/master/Casks/minikube.rb The release job creates a new PR in Homebrew/homebrew-cask with an updated version and SHA256, double check that it's created.

Updating the arch linux package

The Arch Linux AUR is maintained at https://aur.archlinux.org/packages/minikube/. The installer PKGBUILD is hosted in its own repository. The public read-only repository is hosted here https://aur.archlinux.org/minikube.git and the private read-write repository is hosted here ssh://aur@aur.archlinux.org/minikube.git

The repository is tracked in this repo under a submodule installers/linux/arch_linux. Currently, its configured to point at the public readonly repository so if you want to push you should run this command to overwrite

git config submodule.archlinux.url ssh://aur@aur.archlinux.org/minikube.git

To actually update the package, you should bump the version and update the sha512 checksum. You should also run makepkg --printsrcinfo > .SRCINFO to update the srcinfo file. You can edit this manually if you don't have makepkg on your machine.

Verification

After you've finished the release, run this command from the release commit to verify the release was done correctly: make check-release.

Update kubernetes.io docs

If there are major changes, please send a PR to update the official setup guide: Running Kubernetes Locally via Minikube