cluster-api-provider-vsphere
cluster-api-provider-vsphere copied to clipboard
Tasks for v1.11 release cycle
Please see the corresponding sections in release-tasks.md for documentation of individual tasks.
Tasks
Early in the cycle:
- [x] Prepare main branch for development of the new release @chrischdi
- PR: #2950
- [x] Remove previously deprecated code
Release-specific tasks:
- [x] Remove keep alive handler deprecated in: #2896 @zhanggbj
- PR: https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/pull/2984
- [x] Adopt clusterctl upgrade tests to: https://github.com/kubernetes-sigs/cluster-api/pull/10639 (once available for CAPV)
- PR: https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/pull/3050
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)
- Update
README.md
accordingly
- [ ] Bump e2e tests
- Add the new image to
internal/test/helpers/vcsim/model.go
- Bump template env variables in
test/e2e/config/vsphere.yaml
andtest/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 ofhttps://github.com/kubernetes/cloud-provider-vsphere
and runninghelm template charts/vsphere-cpi
- Also bump
- 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
-
- Add the new image to
- [ ] Update ProwJob configuration accordingly
- [ ] Publish new OVA images
Late in the cycle:
- [ ] Bump dependencies
- [ ] Create the new release branch
- [ ] [opt] Cut beta/rc releases
- [ ] Cut the minor release
Continuously:
@chrischdi Whoever takes Prepare main branch for development of the new release, let's take the chance to finalize the corresponding doc section after we finalized what exactly we have to do in the PR
@chrischdi Whoever takes Prepare main branch for development of the new release, let's take the chance to finalize the corresponding doc section after we finalized what exactly we have to do in the PR
PR for docs update: #2951
@adityabhatia @zhanggbj I think we can go ahead with "Remove keep alive handler" if someone has time / is looking for a bit of work :)
@sbueringer I would like to work on it :-)
@sbueringer is Bump the Kubernetes version when we start testing Kubernetes 1.31?
@fabriziopandini I would say it's when we test against 1.31 (instead of just latest-ci)
Removed the test sub-task from this issue, will add it to a new umbrella issue
@chrischdi Assigned to both of us and added to the v1.11 milestone. Please keep especially building the OVA on your radar as it's one of the tasks we have to do after the 1.31 release that takes the most time until we can cut CAPV v1.11
@chrischdi @fabriziopandini
Highlights for the upcoming relase (notes) (based on v1.11.0-beta.0, probably have to amend later)
## Highlights
- Tested with Kubernetes v1.31 & cloud-provider-vsphere v1.31
- Based on Cluster API v1.8
- Bumped to controller-runtime v0.18, k8s.io/* v0.30, controller-gen v0.15
- Bumped to Go 1.22
supervisor mode:
- Significantly improved unit and e2e test coverage (#2995)
- VirtualMachine namingStrategy (#3099)
- Now uses vm-operator v1alpha2 APIs (#3029, #3104)
- Dropped ProviderServiceAccount ConfigMap and deprecated ProviderServiceAccountFinalizer (#3009)
govmomi mode:
- Support for vGPU (#3025)
- Removed the keep alive feature (#2984)
- Use sha256 thumbprint in tests (#3076) (using sha1 thumbprint is now deprecated)
@chrischdi Added a new sub-task to adopt recent CAPI changes in CAPV
Checked diff to latest rc. Nothing to add to the highlights
All PR's for v1.31 should be prepared now.
Waiting for the v1.31.0 release.
All done for v1.11.0 (updated the tasks above)
So should we close this one?
I wasn't sure because of v1.11.1. But let's drop this from this issue and just track it between us?
Didn't get a notification when you added the 👍 :)
/close
@sbueringer: Closing this issue.
In response to this:
Didn't get a notification when you added the 👍 :)
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.