@@ -35,6 +35,7 @@ Metal3.
3535| v1beta1 | v1beta1 | v1.9.X | v1.9.X |
3636| v1beta1 | v1beta1 | v1.10.X | v1.10.X |
3737| v1beta1 | v1beta1 | v1.11.X | v1.11.X |
38+ | v1beta1 | v1beta1 | v1.12.X | v1.12.X |
3839
3940## Deploying the metal3 provider
4041
@@ -53,9 +54,9 @@ need to be manually installed. Example flow of installing Metal3 provider:
5354 level of the logging verbose with a positive integer number, ie. -v5.
5455
5556 ``` shell
56- clusterctl init --core cluster-api:v1.11 .0 \
57- --bootstrap kubeadm:v1.11 .0 \
58- --control-plane kubeadm:v1.11 .0 -v5
57+ clusterctl init --core cluster-api:v1.12 .0 \
58+ --bootstrap kubeadm:v1.12 .0 \
59+ --control-plane kubeadm:v1.12 .0 -v5
5960 ```
6061
61621 . Install Metal3 provider. This will install the latest version of Cluster API
@@ -69,7 +70,7 @@ need to be manually installed. Example flow of installing Metal3 provider:
6970 provider name as follows:
7071
7172 ``` shell
72- clusterctl init --infrastructure metal3:v1.11 .0
73+ clusterctl init --infrastructure metal3:v1.12 .0
7374 ```
7475
75761 . Deploy Baremetal Operator manifests and CRDs. You need to install
@@ -147,6 +148,13 @@ To trigger e2e test on a PR, use the following phrases:
147148- ** /test-centos-e2e-integration-test-main** runs integration e2e
148149 tests with CAPM3 API version v1beta1 and branch main on CentOS
149150
151+ Release-1.12 branch:
152+
153+ - ** /test metal3-ubuntu-e2e-integration-test-release-1-12** runs integration e2e
154+ tests with CAPM3 API version v1beta1 and branch release-1.12 on Ubuntu
155+ - ** /test metal3-centos-e2e-integration-test-release-1-12** runs integration e2e
156+ tests with CAPM3 API version v1beta1 and branch release-1.12 on CentOS
157+
150158Release-1.11 branch:
151159
152160- ** /test metal3-ubuntu-e2e-integration-test-release-1-11** runs integration e2e
@@ -161,26 +169,19 @@ Release-1.10 branch:
161169- ** /test metal3-centos-e2e-integration-test-release-1-10** runs integration e2e
162170 tests with CAPM3 API version v1beta1 and branch release-1.10 on CentOS
163171
164- Release-1.9 branch:
165-
166- - ** /test metal3-ubuntu-e2e-integration-test-release-1-9** runs integration e2e
167- tests with CAPM3 API version v1beta1 and branch release-1.9 on Ubuntu
168- - ** /test metal3-centos-e2e-integration-test-release-1-9** runs integration e2e
169- tests with CAPM3 API version v1beta1 and branch release-1.9 on CentOS
170-
171172## Basic tests
172173
173174Unlike integration tests, basic tests focus on the target cluster creation
174175without involving pivoting from the bootstrap cluster. To run basic tests use:
175176
176177- ** /test metal3-ubuntu-e2e-basic-test-main** runs basic e2e tests with main
177178 branch on Ubuntu
179+ - ** /test metal3-centos-e2e-basic-test-release-1-12** runs basic e2e tests on
180+ release-1.12 branch with centos
178181- ** /test metal3-centos-e2e-basic-test-release-1-11** runs basic e2e tests on
179182 release-1.11 branch with centos
180183- ** /test metal3-centos-e2e-basic-test-release-1-10** runs basic e2e tests on
181184 release-1.10 branch with centos
182- - ** /test metal3-centos-e2e-basic-test-release-1-9** runs basic e2e tests on
183- release-1.9 branch with centos
184185
185186### Feature tests
186187
@@ -199,6 +200,27 @@ feature tests with CAPM3 API version v1beta1 and branch main on Ubuntu
199200- ** /test metal3-centos-e2e-feature-test-main-features** runs e2e non pivot based
200201 feature tests with CAPM3 API version v1beta1 and branch main on CentOS
201202
203+ Release-1.12 branch:
204+
205+ - ** /test metal3-ubuntu-e2e-feature-test-release-1-12-pivoting** runs e2e pivot
206+ based feature tests with CAPM3 API version v1beta1 and branch release-1.12
207+ on Ubuntu
208+ - ** /test metal3-ubuntu-e2e-feature-test-release-1-12-remediation** runs e2e
209+ remediation based feature tests with CAPM3 API version v1beta1 and branch
210+ release-1.12 on Ubuntu
211+ - ** /test metal3-ubuntu-e2e-feature-test-release-1-12-features** runs e2e non
212+ pivot based feature tests with CAPM3 API version v1beta1 and branch release-1.12
213+ on Ubuntu
214+ - ** /test metal3-centos-e2e-feature-test-release-1-12-pivoting** runs e2e pivot
215+ based feature tests with CAPM3 API version v1beta1 and branch release-1.12 on
216+ CentOS
217+ - ** /test metal3-centos-e2e-feature-test-release-1-12-remediation** runs e2e
218+ remediation based feature tests with CAPM3 API version v1beta1 and branch
219+ release-1.12 on CentOS
220+ - ** /test metal3-centos-e2e-feature-test-release-1-12-features** runs e2e non
221+ pivot based feature tests with CAPM3 API version v1beta1 and branch
222+ release-1.12 on CentOS
223+
202224Release-1.11 branch:
203225
204226- ** /test metal3-ubuntu-e2e-feature-test-release-1-11-pivoting** runs e2e pivot
@@ -241,27 +263,6 @@ Release-1.10 branch:
241263 pivot based feature tests with CAPM3 API version v1beta1 and branch
242264 release-1.10 on CentOS
243265
244- Release-1.9 branch:
245-
246- - ** /test metal3-ubuntu-e2e-feature-test-release-1-9-pivoting** runs e2e pivot
247- based feature tests with CAPM3 API version v1beta1 and branch release-1.9
248- on Ubuntu
249- - ** /test metal3-ubuntu-e2e-feature-test-release-1-9-remediation** runs e2e
250- remediation based feature tests with CAPM3 API version v1beta1 and branch
251- release-1.9 on Ubuntu
252- - ** /test metal3-ubuntu-e2e-feature-test-release-1-9-features** runs e2e non
253- pivot based feature tests with CAPM3 API version v1beta1 and branch release-1.9
254- on Ubuntu
255- - ** /test metal3-centos-e2e-feature-test-release-1-9-pivoting** runs e2e pivot
256- based feature tests with CAPM3 API version v1beta1 and branch release-1.9 on
257- CentOS
258- - ** /test metal3-centos-e2e-feature-test-release-1-9-remediation** runs e2e
259- remediation based feature tests with CAPM3 API version v1beta1 and branch
260- release-1.9 on CentOS
261- - ** /test metal3-centos-e2e-feature-test-release-1-9-features** runs e2e non
262- pivot based feature tests with CAPM3 API version v1beta1 and branch
263- release-1.9 on CentOS
264-
265266### Upgrade tests
266267
267268#### Clusterctl upgrade tests
@@ -272,24 +273,25 @@ We run upgrade test on main branch from different releases:
272273- ** /test metal3-e2e-clusterctl-upgrade-test-main** runs e2e clusterctl
273274 upgrade tests on main with Ubuntu
274275
276+ - ** /test metal3-e2e-clusterctl-upgrade-test-release-1-12** runs e2e clusterctl
277+ upgrade tests on release-1.12 with Ubuntu
278+
275279- ** /test metal3-e2e-clusterctl-upgrade-test-release-1-11** runs e2e clusterctl
276280 upgrade tests on release-1.11 with Ubuntu
277281
278282- ** /test metal3-e2e-clusterctl-upgrade-test-release-1-10** runs e2e clusterctl
279283 upgrade tests on release-1.10 with Ubuntu
280284
281- - ** /test metal3-e2e-clusterctl-upgrade-test-release-1-9** runs e2e clusterctl
282- upgrade tests on release-1.9 with Ubuntu
283-
284285#### K8s upgrade tests
285286
286287CAPM3 tests upgrading kubernetes between last 3 releases.
287288The trigger takes the format:
288289` /test metal3-e2e-<from-minor-k8s-v>-<to-minor-k8s-v>-upgrade-test-<branch> `
289290
290291- ** /test metal3-e2e-1-33-1-34-upgrade-test-main**
292+ - ** /test metal3-e2e-1-33-1-34-upgrade-test-release-1-12**
293+ - ** /test metal3-e2e-1-31-1-32-upgrade-test-release-1-11**
291294- ** /test metal3-e2e-1-32-1-33-upgrade-test-release-1-10**
292- - ** /test metal3-e2e-1-31-1-32-upgrade-test-release-1-9**
293295
294296Note:
295297
0 commit comments