You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/release/role-handbooks/release-lead/README.md
+2-7Lines changed: 2 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -92,15 +92,10 @@ Here's an example of how to do this for the `v1.11` release cycle. That means `v
92
92
3. Add the new release, `v1.11`, to the root level `metadata.yaml`.
93
93
4. Remove old `metadata.yaml`'s that are not used anymore in clusterctl upgrade tests, the `test/e2e/data/shared/v1.7` folder in this example.
94
94
4. Adjust cluster templates in `test/e2e/data/infrastructure-docker`:
95
-
1. Create a new `v1.10` folder. It should be created based on the `main` folder and only contain the templates we use in the clusterctl upgrade tests (as of today `cluster-template` and `cluster-template-topology`).
95
+
1. Create a new `v1.10` folder. It should be created based on the `main` folder and only contain the files we use in the clusterctl upgrade tests (as of today `cluster-template-in-memory-topology.yaml` and `clusterclass-in-memory.yaml`).
96
96
2. Remove old folders that are not used anymore in clusterctl upgrade tests, `test/e2e/data/infrastructure-docker/v1.7` in this example.
97
-
5. Add a new Makefile target
98
-
1. Create the new target, `generate-e2e-templates-v1.10` in this example.
99
-
1. Add the new target `v1.10` to `generate-e2e-templates`.
100
-
1. Potentially remove the Makefile target of versions that are not used anymore (if something was removed in 4.2)
101
-
1. In this example we removed `generate-e2e-templates-v1.7` and removed `v1.7` from `generate-e2e-templates`.
102
97
2. Update `create-local-repository.py` and `tools/internal/tilt-prepare/main.go`: `v1.10.99` => `v1.11.99`.
103
-
3. Make sure all tests are green (also run `pull-cluster-api-e2e-full-main` and `pull-cluster-api-e2e-workload-upgrade-1-27-latest-main`).
98
+
3. Make sure all tests are green (also run `pull-cluster-api-e2e-main` and `pull-cluster-api-e2e-upgrade-.*`).
@@ -65,8 +65,8 @@ var _ = Describe("When testing clusterctl upgrades using ClusterClass (v1.11=>cu
65
65
InitWithProvidersContract: "v1beta1",
66
66
// Note: Both InitWithKubernetesVersion and WorkloadKubernetesVersion should be the highest mgmt cluster version supported by the source Cluster API version.
67
67
// When picking this version, please check also the list of versions known by the source Cluster API version (rif. test/infrastructure/kind/mapper.go).
68
-
InitWithKubernetesVersion: "v1.34.0",
69
-
WorkloadKubernetesVersion: "v1.34.0",
68
+
InitWithKubernetesVersion: "v1.35.0",
69
+
WorkloadKubernetesVersion: "v1.35.0",
70
70
MgmtFlavor: "topology",
71
71
WorkloadFlavor: "in-memory-topology",
72
72
UseKindForManagementCluster: true,
@@ -76,9 +76,9 @@ var _ = Describe("When testing clusterctl upgrades using ClusterClass (v1.11=>cu
76
76
})
77
77
78
78
// Note: This test should be changed during "prepare main branch", it should test n-2 => current.
@@ -107,8 +107,8 @@ var _ = Describe("When testing clusterctl upgrades using ClusterClass (v1.12=>cu
107
107
},
108
108
// Note: Both InitWithKubernetesVersion and WorkloadKubernetesVersion should be the highest mgmt cluster version supported by the source Cluster API version.
109
109
// When picking this version, please check also the list of versions known by the source Cluster API version (rif. test/infrastructure/kind/mapper.go).
110
-
InitWithKubernetesVersion: "v1.35.0",
111
-
WorkloadKubernetesVersion: "v1.35.0",
110
+
InitWithKubernetesVersion: "v1.36.1",
111
+
WorkloadKubernetesVersion: "v1.36.1",
112
112
MgmtFlavor: "topology",
113
113
WorkloadFlavor: "in-memory-topology",
114
114
UseKindForManagementCluster: true,
@@ -118,9 +118,9 @@ var _ = Describe("When testing clusterctl upgrades using ClusterClass (v1.12=>cu
118
118
})
119
119
120
120
// Note: This test should be changed during "prepare main branch", it should test n-1 => current.
0 commit comments