The Metrics Server is released on an as-needed basis. The process is as follows:
- An issue is proposing a new release with a changelog since the last release https://github.com/kubernetes-sigs/metrics-server/compare
- At least one OWNER must LGTM this release
- A PR that bumps version hardcoded in code is created and merged
- An OWNER creates a draft GitHub release
- An OWNER creates an issue to release the corresponding Helm chart via the chart release process (below)
- 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 - A PR in kubernetes/k8s.io is created to release images to
k8s.gcr.io
- An OWNER publishes the GitHub release. Once published, release manifests will be automatically added to the release by CI.
- An announcement email is sent to
kubernetes-sig-instrumentation@googlegroups.com
with the subject[ANNOUNCE] metrics-server $VERSION is released
- The release issue is closed
The chart needs to be released in response to a Metrics Server release or on an as-needed basis. The process is as follows:
- An issue is proposing a new chart release
- A PR is opened to update Chart.yaml with the
appVersion
,version
(based on the release changes) andannotations
- The PR triggers the chart linting and testing GitHub action to validate the chart
- The PR is merged and a GitHub action releases the chart