Skip to content

Commit 9550758

Browse files
fabriziopandinifabriziopandini
committed
Update release support and compatibility info
1 parent c94b0ab commit 9550758

File tree

1 file changed

+54
-15
lines changed

1 file changed

+54
-15
lines changed

‎README.md‎

Lines changed: 54 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -29,28 +29,67 @@ Check out the [getting started guide](./docs/getting_started.md) for launching a
2929

3030
------
3131

32+
# CAPV release support
33+
34+
A Cluster API provider vSphere release correspond to a release in the GitHub repository for this project, and the corresponding images published in the Kubernetes docker registry.
35+
The CAPV release calendar will be aligned as much as possible to the Kubernetes and the Cluster API release release dates plus an offset for
36+
performing test/validation after K8s/CAPI release are available (tentatively one or two weeks after both K8s and CAPI release are available).
37+
38+
The CAPV team actively supports the latest two minor releases (N, N-1); support in this context means that we:
39+
40+
- Have CI signal with E2E tests, unit tests, CVE scans etc.
41+
- Accept bug fixes, perform golang or dependency bumps, etc.
42+
- Periodically cut patch releases
43+
- On top of supporting the N and N-1 releases, the CAPV team also maintains CI signal for the CAPV N-2 releases in case we have to do an emergency patch release.
44+
45+
If there is a need for an emergency patch, e.g. to fix a critical security issue, please bring this up to maintainers and it will be considered on a case-by-case basis.
46+
47+
All considered, each CAPV minor release is supported for a period of roughly 12 months:
48+
49+
- The first eight months of this timeframe will be considered the standard support period for a minor release.
50+
- The next four months the minor release will be considered in maintenance mode.
51+
- At the end of the four-month maintenance mode period, the minor release will be considered EOL (end of life) and cherry picks to the associated branch are to be closed soon afterwards.
52+
53+
The table below documents support matrix for Cluster API provider vSphere versions (older versions omitted).
54+
55+
| Minor Release | Status | Supported Until (including maintenance mode) |
56+
|---------------|-------------------------|--------------------------------------------------------------------------------------|
57+
| v1.14.x | Standard support period | in maintenance mode when v1.16.0 will be released, EOL when v1.17.0 will be released |
58+
| v1.13.x | Standard support period | in maintenance mode when v1.15.0 will be released, EOL when v1.16.0 will be released |
59+
| v1.12.x | Maintenance mode | Maintenance mode v1.14.0 release date, EOL when v1.15.0 will be released |
60+
| v1.11.x | EOL | EOL since v1.14.0 release date |
61+
| v1.10.x | EOL | EOL since v1.13.0 release date |
62+
| v1.9.x | EOL | EOL since v1.12.0 release date |
63+
3264
## Compatibility with Cluster API and Kubernetes Versions
3365

34-
This provider's versions are compatible with the following versions of Cluster API:
66+
Compatibility between CAPV releases and Cluster API depends on which Cluster API contract versions supported by CAPI and by which contract version is implemented in CAPV.
67+
68+
CAPV implements following Cluster API contract versions:
69+
70+
| | Cluster API contract version v1beta1 | Cluster API contract version v1beta1 |
71+
|------------|:------------------------------------:|:------------------------------------:|
72+
| CAPV v1.12 | ✓ | x |
73+
| CAPV v1.13 | ✓ | x |
74+
| CAPV v1.14 | ✓ | x |
75+
76+
Contract versions supported by Cluster API are documented in the [versions](https://cluster-api.sigs.k8s.io/reference/versions#cluster-api-release-vs-contract-versions) page in the [Cluster API book](https://cluster-api.sigs.k8s.io).
3577

36-
| | Cluster API v1beta1 (v1.6) | Cluster API v1beta1 (v1.7) | Cluster API v1beta1 (v1.8) | Cluster API v1beta1 (v1.9) |
37-
|----------------------|:--------------------------:|:--------------------------:|:--------------------------:|:--------------------------:|
38-
| CAPV v1beta1 (v1.9) | ✓ | x | x | x |
39-
| CAPV v1beta1 (v1.10) | x | ✓ | x | x |
40-
| CAPV v1beta1 (v1.11) | x | x | ✓ | x |
41-
| CAPV v1beta1 (v1.12) | x | x | x | ✓ |
78+
Also, please note that this project is not validating all the permutations between Cluster API versions and CAPV versions;
79+
below you can find the combinations that are tested in CI:
4280

43-
As CAPV doesn't dictate supported K8s versions, and it supports whatever CAPI supported, about the provider's compatibility with K8s versions, please refer
44-
to [CAPI Supported Kubernetes Versions](https://cluster-api.sigs.k8s.io/reference/versions.html).
81+
| CAPV version | CAPI version used in CI |
82+
|--------------|:-----------------------:|
83+
| CAPV v1.12 | CAPI v1.9 |
84+
| CAPV v1.13 | CAPI v1.10 |
85+
| CAPV v1.14 | CAPI v1.11 |
4586

46-
Basically:
87+
## Compatibility with Kubernetes Versions
4788

48-
- 4 Kubernetes minor releases for the management cluster (N - N-3)
49-
- 6 Kubernetes minor releases for the workload cluster (N - N-5)
89+
CAPV doesn't dictate supported K8s versions, but in practice compatibility with Kubernetes versions is limited by the
90+
compatibility matrix of the Cluster API version you are using in combination with CAPV.
5091

51-
**NOTES:**
52-
* We aim to cut a CAPV minor release approximately one week after the corresponding CAPI minor release is out.
53-
* We aim to cut a CAPV minor or patch release with support for a new Kubernetes minor version approximately 3 business days after releases for CAPI and CPI that support the new Kubernetes version are available.
92+
Please refer to Cluster API 's [Kubernetes versions matrix](https://cluster-api.sigs.k8s.io/reference/versions#kubernetes-versions-support).
5493

5594
## Kubernetes versions with published OVAs
5695

0 commit comments

Comments
 (0)