@@ -23,19 +23,19 @@ should be stable enough to run.
23
23
<a id =" supported-releases " ></a >
24
24
## Currently supported releases
25
25
26
- | Release | Release Date | End of Life | [ Supported Kubernetes versions ] [ s ] | [ Supported OpenShift versions ] [ s ] |
27
- | -------------- | :------------:| :----------------------:| :----------------------------------:| :---------------------------------:|
28
- | [ 1.15] [ ] | Jun 05, 2024 | Release of 1.17 | 1.25 → 1.31 | 4.12 → 4.16 |
29
- | [ 1.14] [ ] | Feb 03, 2024 | Release of 1.16 | 1.24 → 1.31 | 4.11 → 4.16 |
30
- | [ 1.12 LTS] [ ] | May 19, 2023 | May 19, 2025 | 1.22 → 1.31 | 4.9 → 4.16 |
26
+ | Release | Release Date | End of Life | [ Supported Kubernetes / OpenShift Versions ] [ s ] | [ Tested Kubernetes Versions ] [ test ] |
27
+ | : ------------: | :------------:| :----------------------:| :---------------------------------------------- :| :- ---------------------------------:|
28
+ | [ 1.15] [ ] | Jun 05, 2024 | Release of 1.17 | 1.25 → 1.31 / 4.12 → 4.16 | 1.25 → 1.31 |
29
+ | [ 1.14] [ ] | Feb 03, 2024 | Release of 1.16 | 1.24 → 1.31 / 4.11 → 4.16 | 1.24 → 1.29 |
30
+ | [ 1.12 LTS] [ ] | May 19, 2023 | May 19, 2025 | 1.22 → 1.31 / 4.9 → 4.16 | 1.22 → 1.29 |
31
31
32
32
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.
33
33
34
34
## Upcoming releases
35
35
36
- | Release | Release Date | End of Life | [ Supported Kubernetes versions ] [ s ] | [ Supported OpenShift versions ] [ s ] |
37
- | ---------- | :------------:| :----------------:| :----------------------------------: | : ---------------------------------:|
38
- | [ 1.16] [ ] | Oct 03, 2024 | Release of 1.18 | 1.27 → 1.31 | 4.14 → 4.16 |
36
+ | Release | Release Date | End of Life | [ Supported Kubernetes / OpenShift Versions ] [ s ] |
37
+ | : --------: | :------------:| :----------------:| :----------------------------------------------:|
38
+ | [ 1.16] [ ] | Oct 03, 2024 | Release of 1.18 | 1.27 → 1.31 / 4.14 → 4.16 |
39
39
40
40
Dates in the future are not firm commitments and are subject to change.
41
41
@@ -46,19 +46,41 @@ We also maintain detailed [upgrade instructions](https://cert-manager.io/docs/re
46
46
47
47
## Support policy
48
48
49
+ <a id =" supported-vs-tested " ></a >
50
+ ### Supported vs Tested Versions of Kubernetes
51
+
52
+ In general, we aim to run regular end-to-end tests of all Kubernetes versions which we list as supported.
53
+
54
+ For various reasons, this isn't always possible; a big factor is which Kubernetes versions are supported
55
+ by [ Kind] ( https://github.com/kubernetes-sigs/kind ) , which is used in our end-to-end tests.
56
+
57
+ If a Kubernetes version is listed as "tested", you can be sure that we run end-to-end tests of cert-manager
58
+ on that version regularly and we'd fix any issues that we saw in those end-to-end tests.
59
+
60
+ If a Kubernetes version is not listed as "tested" but is listed as "supported", we don't run tests regularly for that
61
+ Kubernetes release, but we _ will_ still respond to and fix any bug reports for that version.
62
+
63
+ 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.
64
+ That means that:
65
+
66
+ - We will fix community-reported issues for cert-manager 1.12 on Kubernetes 1.30 or 1.31
67
+ - We will not run automated tests for cert-manager 1.12 on Kubernetes 1.30 or 1.31
68
+ - We will not generally test or fix issues for cert-manager 1.12 on Kubernetes 1.21 or earlier
69
+
49
70
### What we mean by support
50
71
51
72
Our support window is four months for each release branch. In the below
52
- diagram, ` release-1.2 ` is an example of a release branch. The support
53
- window corresponds to the two latest releases, given that we produce a new
54
- final release every two months. We offer two types of support:
73
+ diagram, ` release-1.2 ` is an example of a release branch.
74
+
75
+ We offer two types of support:
55
76
56
77
- [ Technical support] ( #technical-support ) ,
57
78
- [ Security and bug fixes] ( #bug-fixes-support ) .
58
79
59
80
For example, imagining that the latest release is ` v1.2.0 ` , you can expect
60
- support for both ` v1.2.0 ` and ` v1.1.0 ` . Only the last patch release of each
61
- branch is actually supported.
81
+ support for both ` v1.2.0 ` and ` v1.1.0 ` .
82
+
83
+ Only the last patch release of each branch is supported.
62
84
63
85
``` diagram
64
86
v1.0.0 ^
@@ -187,7 +209,7 @@ We treat OpenShift <abbr title="Extended Update Support">EUS</abbr> as a differe
187
209
We're likely to drop support for older OpenShift EUS before that release reaches EOL to increase the speed at which we can adopt
188
210
newer Kubernetes features.
189
211
190
- 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 >
212
+ 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 >
191
213
for that release. EOL dates often change throughout the lifecycle of a release.
192
214
193
215
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.
294
316
| [ 0.11] [ ] | Oct 10, 2019 | Jan 21, 2020 | 1.9 → 1.21 | 3.09 → 4.7 |
295
317
296
318
[ s ] : #kubernetes-supported-versions
319
+ [ test ] : #supported-vs-tested
297
320
[ 1.16 ] : https://github.com/cert-manager/cert-manager/milestone/38
298
321
[ 1.15 ] : ./release-notes/release-notes-1.15.md
299
322
[ 1.14 ] : ./release-notes/release-notes-1.14.md
0 commit comments