Skip to content

📖 Update release tracking issue template #3614

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 3, 2025
+57 −15
Merged

📖 Update release tracking issue template #3614

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
72 changes: 57 additions & 15 deletions .github/ISSUE_TEMPLATE/release_tracking.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,34 +13,76 @@ Please see the corresponding sections in [release-tasks.md](https://github.com/k

Early in the cycle:
* [ ] [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)
* [ ] Bump to CAPI main
* Prereq: CAPI already bumped to the next controller-runtime / k8s.io/* minor version
* For details, see core CAPI issue: "Tasks to bump to Kubernetes v1.x" (section "Using new Kubernetes dependencies")
* [ ] [Remove previously deprecated code](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/main/docs/release/release-tasks.md#remove-previously-deprecated-code)

Release-specific tasks:

Late in the cycle:
* [ ] [Bump dependencies](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/main/docs/release/release-tasks.md#bump-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)
* [ ] [opt] [Cut beta/rc releases](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/main/docs/release/release-tasks.md#cut-a-release)
* [ ] Before every release ensure we bumped to latest CPI & CAPI & Kubernetes pre-releases
* Bump `CAPI_HACK_TOOLS_VER`
* Bump dependencies in go.mod
* Bump core CAPI provider versions in `test/e2e/config/vsphere.yaml`
* Bump `KUBERNETES*` and `CPI_IMAGE_K8S_VERSION` to latest pre-releases
* Prior art: https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/pull/3424
* [ ] Cherry-pick if the release branch was already cut

After the Kubernetes minor release:
* [ ] Bump the Kubernetes version
* [ ] Publish new OVA images
* Build new OVA images via image-builder
* Make them available in the CI environment
* 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))
* Update `README.md` accordingly
* [ ] Bump e2e tests
* [ ] Build new OVA images with image-builder via a temporary VM in vCenter
* [ ] Publish images to the GCVE CI environment via the vCenter UI:
* Go to the folder view
* [ ] Move `ubuntu-2404` and `flatcar` from `Workload VMs` to `prow/templates`
* If this is not possible for some reason, you can upload `ubuntu-2404` and `flatcar` manually:
* Right-click on the `prow/templates` folder | Deploy OVF Template
* Select local file
* Select a name and folder: `prow/templates`
* Select a compute resource: `k8s-gcve-cluster`
* Select storage: `vsanDatastore`
* Select networks: Destination Network: `k8s-ci`
* Finish & wait for upload to complete (under tasks)
* [ ] Right-click the templates and `Clone to library` to `capv`
* [ ] 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))
* [ ] Delete the temporary VM used to build the images
* [ ] Delete `ubuntu-2204` and `photon` templates from `Workload VMs`
* [ ] Update `README.md` accordingly
* Prior art: https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/pull/3437
* [ ] Bump unit & e2e tests to use the new Kubernetes version
* Add the new image to `internal/test/helpers/vcsim/model.go`
* Bump `KUBEBUILDER_ENVTEST_KUBERNETES_VERSION` in `Makefile`
* Bump template env variables in `test/e2e/config/vsphere.yaml` and `test/e2e/config/config-overrides-example.yaml`
* Also bump `KUBERNETES_VERSION_*`
* Also bump `KUBERNETES_VERSION_LATEST_CI` to the next minor version
* Also bump `CPI_IMAGE_K8S_VERSION`
* 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`
* Bump `KUBERNETES_VERSION_*`
* Bump `KUBERNETES_VERSION_LATEST_CI` to the next minor version
* Bump `VSPHERE_CONTENT_LIBRARY_ITEMS`, `VSPHERE_IMAGE_NAME`, `VSPHERE_TEMPLATE`, `FLATCAR_VSPHERE_TEMPLATE`
* Bump `CPI_IMAGE_K8S_VERSION` & 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 --namespace kube-system > ../../sigs.k8s.io/cluster-api-provider-vsphere/packaging/flavorgen/cloudprovider/cpi/cpi.yaml`
* Bump in:
* `test/e2e/data/infrastructure-vsphere-govmomi/main/clusterclass/patch-vsphere-template.yaml`
* `test/e2e/data/infrastructure-vsphere-supervisor/main/clusterclass/patch-vsphere-template.yaml`
* [ ] Update ProwJob configuration accordingly
* `test/e2e/data/infrastructure-vsphere-supervisor/main/clusterclass/patch-vsphere-template.yaml`
* Prior art: https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/pull/3294
* [ ] Cherry-pick
* [ ] Bump CPI GA release as soon as available
* [ ] Cherry-pick
* [ ] Update ProwJobs to use the Kubernetes GA release
* Prior art: https://github.com/kubernetes/test-infra/pull/34688
* [ ] Start using next Kubernetes release on main
* Prior art: https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/pull/3438

Late in the cycle:
* [ ] [Bump dependencies](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/main/docs/release/release-tasks.md#bump-dependencies)
* [ ] [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)
* [ ] [opt] [Cut beta/rc releases](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/main/docs/release/release-tasks.md#cut-a-release)
Prepare & publish the release:
* [ ] Bump to latest CAPI version (Kubernetes & CPI if necessary)
* Bump `CAPI_HACK_TOOLS_VER`
* Bump dependencies in go.mod
* Bump core CAPI provider versions in `test/e2e/config/vsphere.yaml`
* Bump `KUBERNETES*` and `CPI_IMAGE_K8S_VERSION` to latest releases, if necessary
* Prior art: https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/pull/3291
* [ ] Cherry-pick
* [ ] [Cut the minor release](https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/main/docs/release/release-tasks.md#cut-a-release)

Continuously:
Expand Down