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: .github/ISSUE_TEMPLATE/release_tracking.md
+57-15Lines changed: 57 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,34 +13,76 @@ Please see the corresponding sections in [release-tasks.md](https://github.com/k
13
13
14
14
Early in the cycle:
15
15
*[ ][Prepare main branch for development of the new release](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/main/docs/release/release-tasks.md#prepare-main-branch-for-development-of-the-new-release)
16
+
*[ ] Bump to CAPI main
17
+
* Prereq: CAPI already bumped to the next controller-runtime / k8s.io/* minor version
18
+
* For details, see core CAPI issue: "Tasks to bump to Kubernetes v1.x" (section "Using new Kubernetes dependencies")
*[ ] When cutting RC.0: [Create the new release branch](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/main/docs/release/release-tasks.md#create-a-release-branch)
*[ ] Cherry-pick if the release branch was already cut
20
34
21
35
After the Kubernetes minor release:
22
36
*[ ] Bump the Kubernetes version
23
37
*[ ] Publish new OVA images
24
-
* Build new OVA images via image-builder
25
-
* Make them available in the CI environment
26
-
* Publish them via a GitHub release (e.g. [templates/v1.30.0](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/releases/tag/templates/v1.30.0))
27
-
* Update `README.md` accordingly
28
-
*[ ] Bump e2e tests
38
+
*[ ] Build new OVA images with image-builder via a temporary VM in vCenter
39
+
*[ ] Publish images to the GCVE CI environment via the vCenter UI:
40
+
* Go to the folder view
41
+
*[ ] Move `ubuntu-2404` and `flatcar` from `Workload VMs` to `prow/templates`
42
+
* If this is not possible for some reason, you can upload `ubuntu-2404` and `flatcar` manually:
43
+
* Right-click on the `prow/templates` folder | Deploy OVF Template
44
+
* Select local file
45
+
* Select a name and folder: `prow/templates`
46
+
* Select a compute resource: `k8s-gcve-cluster`
47
+
* Select storage: `vsanDatastore`
48
+
* Select networks: Destination Network: `k8s-ci`
49
+
* Finish & wait for upload to complete (under tasks)
50
+
*[ ] Right-click the templates and `Clone to library` to `capv`
51
+
*[ ] Publish them via a GitHub release (e.g. [templates/v1.30.0](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/releases/tag/templates/v1.30.0))
52
+
*[ ] Delete the temporary VM used to build the images
53
+
*[ ] Delete `ubuntu-2204` and `photon` templates from `Workload VMs`
*[ ] Bump unit & e2e tests to use the new Kubernetes version
29
57
* Add the new image to `internal/test/helpers/vcsim/model.go`
58
+
* Bump `KUBEBUILDER_ENVTEST_KUBERNETES_VERSION` in `Makefile`
30
59
* Bump template env variables in `test/e2e/config/vsphere.yaml` and `test/e2e/config/config-overrides-example.yaml`
31
-
* Also bump `KUBERNETES_VERSION_*`
32
-
* Also bump `KUBERNETES_VERSION_LATEST_CI` to the next minor version
33
-
* Also bump `CPI_IMAGE_K8S_VERSION`
34
-
* Regenerate `packaging/flavorgen/cloudprovider/cpi/cpi.yaml` by checking out the release tag of `https://github.com/kubernetes/cloud-provider-vsphere` and running `helm template charts/vsphere-cpi`
60
+
* Bump `KUBERNETES_VERSION_*`
61
+
* Bump `KUBERNETES_VERSION_LATEST_CI` to the next minor version
*[ ][Create the new release branch](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/main/docs/release/release-tasks.md#create-a-release-branch)
0 commit comments