Skip to content

Latest commit

 

History

History
23 lines (18 loc) · 1.6 KB

RELEASE.md

File metadata and controls

23 lines (18 loc) · 1.6 KB
Raw

Release Process

The Metrics Server is released on an as-needed basis. The process is as follows:

  1. An issue is proposing a new release with a changelog since the last release
  2. At least one OWNER must LGTM this release
  3. A PR that bumps version hardcoded in code is created and merged
  4. An OWNER creates a draft GitHub release
  5. An OWNER creates an issue to release the corresponding Helm chart via the chart release process (below)
  6. An OWNER creates a release tag using GIT_TAG=$VERSION make release-tag and waits for prow.k8s.io to build and push new images to gcr.io/k8s-staging-metrics-server
  7. A PR in kubernetes/k8s.io is created to release images to k8s.gcr.io
  8. An OWNER publishes the GitHub release. Once published, release manifests will be automatically added to the release by CI.
  9. An announcement email is sent to kubernetes-sig-instrumentation@googlegroups.com with the subject [ANNOUNCE] metrics-server $VERSION is released
  10. The release issue is closed

Chart Release Process

The chart needs to be released in response to a Metrics Server release or on an as-needed basis. The process is as follows:

  1. An issue is proposing a new chart release
  2. A PR is opened to update Chart.yaml with the appVersion, version (based on the release changes) and annotations
  3. The PR triggers the chart linting and testing GitHub action to validate the chart
  4. The PR is merged and a GitHub action releases the chart