Skip to content
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

Open
3 of 12 tasks
sbueringer opened this issue Apr 25, 2024 · 7 comments
Open
3 of 12 tasks

Tasks for v1.11 release cycle #2945

sbueringer opened this issue Apr 25, 2024 · 7 comments

Comments

@sbueringer
Copy link
Member

sbueringer commented Apr 25, 2024

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:

  • 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 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 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

Late in the cycle:

Continuously:

@sbueringer
Copy link
Member Author

sbueringer commented Apr 25, 2024

@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
Copy link
Member

@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

@sbueringer
Copy link
Member Author

sbueringer commented May 2, 2024

@adityabhatia @zhanggbj I think we can go ahead with "Remove keep alive handler" if someone has time / is looking for a bit of work :)

@zhanggbj
Copy link
Contributor

zhanggbj commented May 6, 2024

@sbueringer I would like to work on it :-)

@fabriziopandini
Copy link
Member

@sbueringer is Bump the Kubernetes version when we start testing Kubernetes 1.31?

@sbueringer
Copy link
Member Author

sbueringer commented May 10, 2024

@fabriziopandini I would say it's when we test against 1.31 (instead of just latest-ci)

@sbueringer
Copy link
Member Author

Removed the test sub-task from this issue, will add it to a new umbrella issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants