Merge pull request #1575 from cert-manager/master

Merging master into release-next

content/docs/releases/README.md

@@ -23,19 +23,19 @@ should be stable enough to run.
 <a id="supported-releases"></a>
 ## Currently supported releases
 
-| Release | Release Date | End of Life | [Supported Kubernetes versions][s] | [Supported OpenShift versions][s] |
-|--------------|:------------:|:----------------------:|:----------------------------------:|:---------------------------------:|
-| [1.15][] | Jun 05, 2024 | Release of 1.17 | 1.25 → 1.31    | 4.12 → 4.16 |
-| [1.14][] | Feb 03, 2024 | Release of 1.16 | 1.24 → 1.31    | 4.11 → 4.16 |
-| [1.12 LTS][] | May 19, 2023 | May 19, 2025 | 1.22 → 1.31    | 4.9 → 4.16  |
+| Release | Release Date | End of Life | [Supported Kubernetes / OpenShift Versions][s] | [Tested Kubernetes Versions][test] |
+|:------------:|:------------:|:----------------------:|:----------------------------------------------:|:----------------------------------:|
+| [1.15][] | Jun 05, 2024 | Release of 1.17 |  1.25 → 1.31 / 4.12 → 4.16 | 1.25 → 1.31 |
+| [1.14][] | Feb 03, 2024 | Release of 1.16 |  1.24 → 1.31 / 4.11 → 4.16 | 1.24 → 1.29 |
+| [1.12 LTS][] | May 19, 2023 | May 19, 2025 |  1.22 → 1.31 / 4.9 → 4.16 | 1.22 → 1.29 |
 
 cert-manager 1.12 is a Long Term Support (LTS) release sponsored by [Venafi](https://www.venafi.com/). It will continue to be supported for at least 2 years from release.
 
 ## Upcoming releases
 
-| Release | Release Date | End of Life | [Supported Kubernetes versions][s] | [Supported OpenShift versions][s] |
-|----------|:------------:|:----------------:|:----------------------------------:|:---------------------------------:|
-| [1.16][] | Oct 03, 2024 | Release of 1.18 | 1.27 → 1.31  | 4.14 → 4.16  |
+| Release | Release Date | End of Life | [Supported Kubernetes / OpenShift Versions][s] |
+|:--------:|:------------:|:----------------:|:----------------------------------------------:|
+| [1.16][] | Oct 03, 2024 | Release of 1.18 | 1.27 → 1.31 / 4.14 → 4.16 |
 
 Dates in the future are not firm commitments and are subject to change.
 
@@ -46,19 +46,41 @@ We also maintain detailed [upgrade instructions](https://cert-manager.io/docs/re
 
 ## Support policy
 
+<a id="supported-vs-tested"></a>
+### Supported vs Tested Versions of Kubernetes
+
+In general, we aim to run regular end-to-end tests of all Kubernetes versions which we list as supported.
+
+For various reasons, this isn't always possible; a big factor is which Kubernetes versions are supported
+by [Kind](https://github.com/kubernetes-sigs/kind), which is used in our end-to-end tests.
+
+If a Kubernetes version is listed as "tested", you can be sure that we run end-to-end tests of cert-manager
+on that version regularly and we'd fix any issues that we saw in those end-to-end tests.
+
+If a Kubernetes version is not listed as "tested" but is listed as "supported", we don't run tests regularly for that
+Kubernetes release, but we _will_ still respond to and fix any bug reports for that version.
+
+For example, cert-manager 1.12 LTS might list supported versions of Kubernetes as 1.22 → 1.31 but only test 1.22 → 1.29.
+That means that:
+
+- We will fix community-reported issues for cert-manager 1.12 on Kubernetes 1.30 or 1.31
+- We will not run automated tests for cert-manager 1.12 on Kubernetes 1.30 or 1.31
+- We will not generally test or fix issues for cert-manager 1.12 on Kubernetes 1.21 or earlier
+
 ### What we mean by support
 
 Our support window is four months for each release branch. In the below
-diagram, `release-1.2` is an example of a release branch. The support
-window corresponds to the two latest releases, given that we produce a new
-final release every two months. We offer two types of support:
+diagram, `release-1.2` is an example of a release branch.
+
+We offer two types of support:
 
 - [Technical support](#technical-support),
 - [Security and bug fixes](#bug-fixes-support).
 
 For example, imagining that the latest release is `v1.2.0`, you can expect
-support for both `v1.2.0` and `v1.1.0`. Only the last patch release of each
-branch is actually supported.
+support for both `v1.2.0` and `v1.1.0`.
+
+Only the last patch release of each branch is supported.
 
 ```diagram
  v1.0.0 ^
@@ -187,7 +209,7 @@ We treat OpenShift <abbr title="Extended Update Support">EUS</abbr> as a differe
 We're likely to drop support for older OpenShift EUS before that release reaches EOL to increase the speed at which we can adopt
 newer Kubernetes features.
 
-The table below lists the major Kubernetes distributions we check. In brackets next to each release is the <abbr title="End-of-life">EOL</abbr>
+The table below lists the major Kubernetes distributions we check. In parentheses next to each release is the <abbr title="End-of-life">EOL</abbr>
 for that release. EOL dates often change throughout the lifecycle of a release.
 
 The "Oldest Kubernetes Release" is the oldest release we deemed relevant to the next cert-manager release, as of 2024-09-25
@@ -294,6 +316,7 @@ are no longer supported.
 | [0.11][] | Oct 10, 2019 | Jan 21, 2020 | 1.9 → 1.21 | 3.09 → 4.7 |
 
 [s]: #kubernetes-supported-versions
+[test]: #supported-vs-tested
 [1.16]: https://github.com/cert-manager/cert-manager/milestone/38
 [1.15]: ./release-notes/release-notes-1.15.md
 [1.14]: ./release-notes/release-notes-1.14.md

klone.yaml

@@ -10,30 +10,30 @@ targets:
  - folder_name: boilerplate
  repo_url: https://github.com/cert-manager/makefile-modules.git
  repo_ref: main
- repo_hash: 3cf24410bca85e4b3f39f71882c8655b2d34464c
+ repo_hash: 279334d152866c753421232cf237dab891fbaf5f
  repo_path: modules/boilerplate
  - folder_name: generate-verify
  repo_url: https://github.com/cert-manager/makefile-modules.git
  repo_ref: main
- repo_hash: 3cf24410bca85e4b3f39f71882c8655b2d34464c
+ repo_hash: 279334d152866c753421232cf237dab891fbaf5f
  repo_path: modules/generate-verify
  - folder_name: help
  repo_url: https://github.com/cert-manager/makefile-modules.git
  repo_ref: main
- repo_hash: 3cf24410bca85e4b3f39f71882c8655b2d34464c
+ repo_hash: 279334d152866c753421232cf237dab891fbaf5f
  repo_path: modules/help
  - folder_name: klone
  repo_url: https://github.com/cert-manager/makefile-modules.git
  repo_ref: main
- repo_hash: 3cf24410bca85e4b3f39f71882c8655b2d34464c
+ repo_hash: 279334d152866c753421232cf237dab891fbaf5f
  repo_path: modules/klone
  - folder_name: repository-base
  repo_url: https://github.com/cert-manager/makefile-modules.git
  repo_ref: main
- repo_hash: 3cf24410bca85e4b3f39f71882c8655b2d34464c
+ repo_hash: 279334d152866c753421232cf237dab891fbaf5f
  repo_path: modules/repository-base
  - folder_name: tools
  repo_url: https://github.com/cert-manager/makefile-modules.git
  repo_ref: main
- repo_hash: 3cf24410bca85e4b3f39f71882c8655b2d34464c
+ repo_hash: 279334d152866c753421232cf237dab891fbaf5f
  repo_path: modules/tools

make/_shared/tools/00_mod.mk

@@ -159,7 +159,7 @@ ADDITIONAL_TOOLS ?=
 tools += $(ADDITIONAL_TOOLS)
 
 # https://go.dev/dl/
-VENDORED_GO_VERSION := 1.23.1
+VENDORED_GO_VERSION := 1.23.2
 
 # Print the go version which can be used in GH actions
 .PHONY: print-go-version
@@ -374,10 +374,10 @@ $(call for_each_kv,go_dependency,$(go_dependencies))
 # File downloads #
 ##################
 
-go_linux_amd64_SHA256SUM=49bbb517cfa9eee677e1e7897f7cf9cfdbcf49e05f61984a2789136de359f9bd
-go_linux_arm64_SHA256SUM=faec7f7f8ae53fda0f3d408f52182d942cc89ef5b7d3d9f23ff117437d4b2d2f
-go_darwin_amd64_SHA256SUM=488d9e4ca3e3ed513ee4edd91bef3a2360c65fa6d6be59cf79640bf840130a58
-go_darwin_arm64_SHA256SUM=e223795ca340e285a760a6446ce57a74500b30e57469a4109961d36184d3c05a
+go_linux_amd64_SHA256SUM=542d3c1705f1c6a1c5a80d5dc62e2e45171af291e755d591c5e6531ef63b454e
+go_linux_arm64_SHA256SUM=f626cdd92fc21a88b31c1251f419c17782933a42903db87a174ce74eeecc66a9
+go_darwin_amd64_SHA256SUM=445c0ef19d8692283f4c3a92052cc0568f5a048f4e546105f58e991d4aea54f5
+go_darwin_arm64_SHA256SUM=d87031194fe3e01abdcaf3c7302148ade97a7add6eac3fec26765bcb3207b80f
 
 .PRECIOUS: $(DOWNLOAD_DIR)/tools/go@$(VENDORED_GO_VERSION)_$(HOST_OS)_$(HOST_ARCH).tar.gz
 $(DOWNLOAD_DIR)/tools/go@$(VENDORED_GO_VERSION)_$(HOST_OS)_$(HOST_ARCH).tar.gz: | $(DOWNLOAD_DIR)/tools