-
Notifications
You must be signed in to change notification settings - Fork 296
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.
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
Tasks for v1.11 release cycle #2945
Comments
@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 |
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:
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. |
Please see the corresponding sections in release-tasks.md for documentation of individual tasks.
Tasks
Early in the cycle:
Release-specific tasks:
After the Kubernetes minor release:
README.md
accordinglyinternal/test/helpers/vcsim/model.go
test/e2e/config/vsphere.yaml
andtest/e2e/config/config-overrides-example.yaml
KUBERNETES_VERSION_*
KUBERNETES_VERSION_LATEST_CI
to the next minor versionCPI_IMAGE_K8S_VERSION
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
test/e2e/data/infrastructure-vsphere-govmomi/main/clusterclass/patch-vsphere-template.yaml
test/e2e/data/infrastructure-vsphere-supervisor/main/clusterclass/patch-vsphere-template.yaml
Late in the cycle:
Continuously:
The text was updated successfully, but these errors were encountered: