Release sync - v0.13.0 (#2215)

* make: Update kubeconform target versions

* docs: Update changelog

* docs: Update release details and matrix

* Update support matrix and ci to include 1.26
This commit is contained in:
Philip Gough
2023-09-08 13:54:26 +01:00
committed by GitHub
parent 76ebaeeafe
commit 7fafc4cadc
5 changed files with 39 additions and 24 deletions

View File

@@ -1,10 +1,13 @@
# Release schedule
Kube-prometheus has a somehow predictable release schedule, releases were
historically cut in sync with OpenShift releases as per downstream needs. So
far there hasn't been any problem with this schedule since it is also in sync
with Kubernetes releases. So for every new Kubernetes release, there is a new
release of kube-prometheus, although it tends to happen later.
historically cut in sync with OpenShift releases as per downstream needs.
This has been changed in favour of tracking upstream Kubernetes releases due
to changing needs and requirements in the OpenShift release process.
For every new Kubernetes release, there will be a corresponding new release
of kube-prometheus, although it tends to happen later.
# How to cut a new release
@@ -30,12 +33,6 @@ master. Try to avoid that situation.
Maintaining the release branches for older minor releases happens on a best
effort basis.
## Cut a release of kubernetes-mixins
kube-prometheus and kubernetes-mixins releases are tied, so before cutting the
release of kube-prometheus we should make sure that the same release of
kubernetes-mixins exists.
## Update components version
Every release of kube-prometheus should include the latest versions of each