Release 4.13 Checklist

[jan--f]

Feature freeze release checklist

Golang projects and backports

• update downstream backport of openshift/node_exporter
• update downstream backport of openshift/prometheus
• update downstream backport of openshift/alertmanager
• update downstream backport of openshift/thanos
• update downstream backport of openshift/prometheus-operator
• update downstream backport of openshift/kube-state-metrics
• update downstream backport of openshift/kube-rbac-proxy
• update downstream backport of openshift/k8s-prometheus-adapter

Jsonnet dependencies

• cut new release in kubernetes-monitoring/kubernetes-mixin
• cut new release in thanos-io/kube-thanos
• cut new release in prometheus-operator/kube-prometheus

Cluster Monitoring Operator

• update and pin jsonnet dependencies in jsonnet/jsonnetfile.json.
  • example: https://github.com/openshift/cluster-monitoring-operator/blob/release-4.3/jsonnet/jsonnetfile.json
  • dependencies should be pinned to branches released in previous paragraph
  • ensure jsonnet/version.json file is tracking up-to-date component versions by running make versions and regenerating assets/ if necessary
• update golang dependencies in go.mod and hack/tools/go.mod files.
  • most important are dependencies on prometheus-operator and kubernetes components
  • update the tooling prometheus dependency to be in sync with the main one

[jan--f]

I checked off the golang updates since syncbot keeps those updated for us.

I propose to forego the releases of our jsonnet upstreams. This always takes a fair amount of effort and time and we can simply ping a desired commit for our release as well.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[jan--f]

/close

[openshift-ci]

@jan--f: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.