Skip to content

Latest commit

 

History

History
29 lines (24 loc) · 1.79 KB

RELEASE.md

File metadata and controls

29 lines (24 loc) · 1.79 KB
Raw

Release Guide

  1. An issue is proposing a new release with a changelog since the last release.
  2. Make sure your repo is clean by git's standards.
  3. Tag the repository from the master branch (from the release-1.19 branch for a patch release) and push the tag VERSION=v0.19.0 git tag -m $VERSION $VERSION; git push origin $VERSION.
  4. An OWNER creates a release branch git checkout -b release-1.19. (not required for patch releases)
  5. Add the prow-job settings for the new release branch here.
  6. Push the release branch to the kube-scheduler-simulator repo and ensure branch protection is enabled. (not required for patch releases)
  7. Publish a draft release using the tag you created in 3.
  8. Perform the image promotion process.
  9. Publish release.
  10. Email kubernetes-sig-scheduling@googlegroups.com to announce the release.

Notes

See post-kube-scheduler-simulator-push-images dashboard for staging registry image build job status.

View the kube-scheduler-simulator staging registry using this URL in a web browser or use the below gcloud commands.

List images in staging registry.

gcloud container images list --repository gcr.io/k8s-staging-sched-simulator

List simulator-backend and simulator-frontend image tags in the staging registry.

gcloud container images list-tags gcr.io/k8s-staging-sched-simulator/simulator-backend
gcloud container images list-tags gcr.io/k8s-staging-sched-simulator/simulator-frontend