diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index 3362f30470f3..8087151a5160 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -1,6 +1,6 @@ --- name: 🐛 Bug report -about: Tell us about a problem you are experiencing +about: Tell us about a problem you are experiencing. title: '' labels: '' assignees: '' diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md index 7d19611b5116..4404765eee2a 100644 --- a/.github/ISSUE_TEMPLATE/feature_request.md +++ b/.github/ISSUE_TEMPLATE/feature_request.md @@ -1,6 +1,6 @@ --- name: ✨ Feature request -about: Suggest an idea for this project +about: Suggest an idea for this project. title: '' labels: '' assignees: '' diff --git a/.github/ISSUE_TEMPLATE/kubernetes_bump.md b/.github/ISSUE_TEMPLATE/kubernetes_bump.md new file mode 100644 index 000000000000..e5c67eecc022 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/kubernetes_bump.md @@ -0,0 +1,68 @@ +--- +name: 🚀 Kubernetes bump +about: "[Only for release team lead] Create an issue to track tasks to support a new Kubernetes minor release." +title: Tasks to bump to Kubernetes v1. +labels: '' +assignees: '' + +--- + +This issue is tracking the tasks that should be implemented **after** the Kubernetes minor release has been released. + +## Tasks + +Prerequisites: +* [ ] Decide which Cluster API release series will support the new Kubernetes version + * If feasible we usually cherry-pick the changes back to the latest release series. + +### Supporting managing and running on the new Kubernetes version + +This section contains tasks to update our book, e2e testing and CI to use and test the new Kubernetes version +as well as changes to Cluster API that we might have to make to support the new Kubernetes version. All of these +changes should be cherry-picked to all release series that will support the new Kubernetes version. + +* [ ] Modify quickstart and CAPD to use the new Kubernetes release: + * Bump the Kubernetes version in: + * `test/*`: search for occurrences of the previous Kubernetes version + * `Tiltfile` + * Ensure the latest available kind version is used as well. + * Verify the quickstart manually + * Prior art: #7156 +* [ ] Job configurations: + * For all releases which will support the new Kubernetes version: + * Update `INIT_WITH_KUBERNETES_VERSION`. + * Add new periodic upgrade jobs . + * Adjust presubmit jobs so that we have the latest upgrade jobs available on PRs. + * Prior art: https://github.com/kubernetes/test-infra/pull/27421 +* [ ] Update book: + * Update supported versions in `versions.md` + * Update job documentation in `jobs.md` + * Prior art: #7194 #7196 +* [ ] Issues specific to the Kubernetes minor release: + * Sometimes there are adjustments that we have to make in Cluster API to be able to support + a new Kubernetes minor version. Please add these issues here when they are identified. + +### Using new Kubernetes dependencies + +This section contains tasks to update Cluster API to use the latest Kubernetes Go dependencies and related topics +like using the right Go version and build images. These changes are only made on the main branch. We don't +need them in older releases as they are not necessary to manage workload clusters of the new Kubernetes version or +run the Cluster API controllers on the new Kubernetes version. + +* [ ] Ensure there is a new controller-runtime minor release which uses the new Kubernetes Go dependencies. +* [ ] Update our Prow jobs for the `main` branch to use the correct `kubekins-e2e` image + * It is recommended to have one PR for presubmit and one for periodic jobs to reduce the risk of breaking the periodic jobs. + * Prior art: presubmit jobs: https://github.com/kubernetes/test-infra/pull/27311 + * Prior art: periodic jobs: https://github.com/kubernetes/test-infra/pull/27311 +* [ ] Bump the Go version in Cluster API: (if Kubernetes is using a new Go minor version) + * Search for the currently used Go version across the repository and update it + * We have to at least modify it in: `.github/workflows`, `hack/ensure-go.sh`, `.golangci.yml`, `cloudbuild*.yaml`, `go.mod`, `Makefile`, `netlify.toml`, `Tiltfile` + * Prior art: #7135 +* [ ] Bump controller-runtime +* [ ] Bump controller-tools +* [ ] Bump the Kubernetes version used in integration tests via `KUBEBUILDER_ENVTEST_KUBERNETES_VERSION` in `Makefile` + * **Note**: This PR should be cherry-picked as well. It is part of this section as it depends on kubebuilder/controller-runtime + releases and is not strictly necessary for [Supporting managing and running on the new Kubernetes version](#supporting-managing-and-running-on-the-new-kubernetes-version). + * Prior art: #7193 +* [ ] Bump conversion-gen via `CONVERSION_GEN_VER` in `Makefile` + * Prior art: #7118 diff --git a/.github/ISSUE_TEMPLATE/release_tracking.md b/.github/ISSUE_TEMPLATE/release_tracking.md index 0c5e34b565ef..83e5b8053c22 100644 --- a/.github/ISSUE_TEMPLATE/release_tracking.md +++ b/.github/ISSUE_TEMPLATE/release_tracking.md @@ -1,13 +1,14 @@ --- name: 🚋 Release cycle tracking -about: Create a new release cycle tracking issue for a minor release +about: Create a new release cycle tracking issue for a Cluster API minor release +about: "[Only for release team lead] Create an issue to track tasks for a Cluster API minor release." title: Tasks for v release cycle labels: '' assignees: '' --- -Please see the corresponding section in [release-tasks.md](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md) for documentation of individual tasks. +Please see the corresponding section in [release-tasks.md](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md) for documentation of individual tasks. ## Tasks @@ -16,65 +17,65 @@ Please see the corresponding section in [release-tasks.md](https://github.com/sb * The following is based on the v1.4 release cycle. Modify according to the tracked release cycle. Week -3 to 1: -* [ ] [Release Lead] [Set a tentative release date for the minor release](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#set-a-tentative-release-date-for-the-minor-release) -* [ ] [Release Lead] [Assemble release team](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#assemble-release-team) +* [ ] [Release Lead] [Set a tentative release date for the minor release](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#set-a-tentative-release-date-for-the-minor-release) +* [ ] [Release Lead] [Assemble release team](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#assemble-release-team) Week 1: -* [ ] [Release Lead] [Finalize release schedule and team](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#finalize-release-schedule-and-team) -* [ ] [Release Lead] [Prepare main branch for development of the new release](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#prepare-main-branch-for-development-of-the-new-release) -* [ ] [Communications Manager] [Add docs to collect release notes for users and migration notes for provider implementers](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#add-docs-to-collect-release-notes-for-users-and-migration-notes-for-provider-implementers) -* [ ] [Communications Manager] [Update supported versions](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#update-supported-versions) +* [ ] [Release Lead] [Finalize release schedule and team](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#finalize-release-schedule-and-team) +* [ ] [Release Lead] [Prepare main branch for development of the new release](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#prepare-main-branch-for-development-of-the-new-release) +* [ ] [Communications Manager] [Add docs to collect release notes for users and migration notes for provider implementers](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#add-docs-to-collect-release-notes-for-users-and-migration-notes-for-provider-implementers) +* [ ] [Communications Manager] [Update supported versions](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#update-supported-versions) Week 1 to 4: -* [ ] [Release Lead] [Track] [Remove previously deprecated code](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#track-remove-previously-deprecated-code) +* [ ] [Release Lead] [Track] [Remove previously deprecated code](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#track-remove-previously-deprecated-code) Week 6: -* [ ] [Release Lead] [Cut the v1.3.1 release](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#repeatedly-cut-a-release) +* [ ] [Release Lead] [Cut the v1.3.1 release](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#repeatedly-cut-a-release) Week 9: -* [ ] [Release Lead] [Cut the v1.3.2 release](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#repeatedly-cut-a-release) +* [ ] [Release Lead] [Cut the v1.3.2 release](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#repeatedly-cut-a-release) Week 11 to 12: -* [ ] [Release Lead] [Track] [Bump dependencies](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#track-bump-dependencies) +* [ ] [Release Lead] [Track] [Bump dependencies](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#track-bump-dependencies) Week 13: -* [ ] [Release Lead] [Cut the v1.4.0-beta.0 release](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#repeatedly-cut-a-release) -* [ ] [Release Lead] [Cut the v1.3.3 release](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#repeatedly-cut-a-release) -* [ ] [Release Lead] [Create a new GitHub milestone for the next release](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#create-a-new-github-milestone-for-the-next-release) +* [ ] [Release Lead] [Cut the v1.4.0-beta.0 release](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#repeatedly-cut-a-release) +* [ ] [Release Lead] [Cut the v1.3.3 release](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#repeatedly-cut-a-release) +* [ ] [Release Lead] [Create a new GitHub milestone for the next release](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#create-a-new-github-milestone-for-the-next-release) Week 14: -* [ ] [Release Lead] [Cut the v1.4.0-beta.1 release](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#repeatedly-cut-a-release) +* [ ] [Release Lead] [Cut the v1.4.0-beta.1 release](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#repeatedly-cut-a-release) * [ ] [Release Lead] Select release lead for the next release cycle Week 15: -* [ ] [Release Lead] [Create the release-1.4 release branch](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#create-a-release-branch) -* [ ] [Release Lead] [Cut the v1.4.0-rc.0 release](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#repeatedly-cut-a-release) -* [ ] [CI Manager] [Setup jobs and dashboards for the release-1.4 release branch](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#setup-jobs-and-dashboards-for-a-new-release-branch) -* [ ] [Communications Manager] [Ensure the book for the new release is available](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#ensure-the-book-for-the-new-release-is-available) +* [ ] [Release Lead] [Create the release-1.4 release branch](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#create-a-release-branch) +* [ ] [Release Lead] [Cut the v1.4.0-rc.0 release](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#repeatedly-cut-a-release) +* [ ] [CI Manager] [Setup jobs and dashboards for the release-1.4 release branch](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#setup-jobs-and-dashboards-for-a-new-release-branch) +* [ ] [Communications Manager] [Ensure the book for the new release is available](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#ensure-the-book-for-the-new-release-is-available) Week 15 to 17: -* [ ] [Communications Manager] [Polish release notes](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#polish-release-notes) +* [ ] [Communications Manager] [Polish release notes](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#polish-release-notes) Week 16: -* [ ] [Release Lead] [Cut the v1.4.0-rc.1 release](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#repeatedly-cut-a-release) +* [ ] [Release Lead] [Cut the v1.4.0-rc.1 release](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#repeatedly-cut-a-release) Week 17: -* [ ] [Release Lead] [Cut the v1.4.0 release](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#repeatedly-cut-a-release) -* [ ] [Release Lead] [Cut the v1.3.4 release](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#repeatedly-cut-a-release) +* [ ] [Release Lead] [Cut the v1.4.0 release](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#repeatedly-cut-a-release) +* [ ] [Release Lead] [Cut the v1.3.4 release](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#repeatedly-cut-a-release) * [ ] [Release Lead] Organize release retrospective -* [ ] [Communications Manager] [Change production branch in Netlify to the new release branch](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#change-production-branch-in-netlify-to-the-new-release-branch) -* [ ] [Communications Manager] [Update clusterctl links in the quickstart](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#update-clusterctl-links-in-the-quickstart) +* [ ] [Communications Manager] [Change production branch in Netlify to the new release branch](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#change-production-branch-in-netlify-to-the-new-release-branch) +* [ ] [Communications Manager] [Update clusterctl links in the quickstart](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#update-clusterctl-links-in-the-quickstart) Continuously: -* [Release lead] [Maintain the GitHub release milestone](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#continuously-maintain-the-github-release-milestone) -* [Communications Manager] [Communicate key dates to the community](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#continuously-communicate-key-dates-to-the-community) +* [Release lead] [Maintain the GitHub release milestone](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#continuously-maintain-the-github-release-milestone) +* [Communications Manager] [Communicate key dates to the community](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#continuously-communicate-key-dates-to-the-community) * [Communications Manager] Improve release process documentation * [Communications Manager] Maintain and improve user facing documentation about releases, release policy and release calendar -* [CI Manager] [Monitor CI signal](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#continuously-monitor-ci-signal) -* [CI Manager] [Reduce the amount of flaky tests](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#continuously-reduce-the-amount-of-flaky-tests) -* [CI Manager] [Bug triage](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#continuously-bug-triage) +* [CI Manager] [Monitor CI signal](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#continuously-monitor-ci-signal) +* [CI Manager] [Reduce the amount of flaky tests](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#continuously-reduce-the-amount-of-flaky-tests) +* [CI Manager] [Bug triage](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#continuously-bug-triage) * [CI Manager] Maintain and improve release automation, tooling & related developer docs If and when necessary: -* [ ] [Release Lead] [Track] [Bump the Cluster API apiVersion](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#optional-track-bump-the-cluster-api-apiversion) -* [ ] [Release Lead] [Track] [Bump the Kubernetes version](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-tasks.md#optional-track-bump-the-kubernetes-version) +* [ ] [Release Lead] [Track] [Bump the Cluster API apiVersion](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#optional-track-bump-the-cluster-api-apiversion) +* [ ] [Release Lead] [Track] [Bump the Kubernetes version](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#optional-track-bump-the-kubernetes-version) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8a17d811cebd..fc89821b5cfe 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -51,7 +51,7 @@ come up, including gaps in documentation! If you're a more experienced contributor, looking at unassigned issues in the next release milestone is a good way to find work that has been prioritized. For example, if the latest minor release is `v1.0`, the next release milestone is `v1.1`. -Help and contributions are very welcome in the form of code contributions but also in helping to moderate office hours, triaging issues, fixing/investigating flaky tests, being part of the [release team](https://github.com/sbueringer/cluster-api/blob/pr-release-tasks/docs/release/release-team.md), helping new contributors with their questions, reviewing proposals, etc. +Help and contributions are very welcome in the form of code contributions but also in helping to moderate office hours, triaging issues, fixing/investigating flaky tests, being part of the [release team](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-team.md), helping new contributors with their questions, reviewing proposals, etc. ## Versioning diff --git a/docs/release/release-1.3.md b/docs/release/release-1.3.md index a55704db5c7d..3607c17c428b 100644 --- a/docs/release/release-1.3.md +++ b/docs/release/release-1.3.md @@ -10,18 +10,18 @@ The following table shows the preliminary dates for the `v1.3` release cycle. | **What** | **When** | **Week** | |------------------------------------------------------|-------------------------------|----------| | Start of Release Cycle | Monday 18th July 2022 | week 1 | -| *v1.2.1 released* | Monday 15th August 2022 | week 5 | -| *v1.2.2 released* | Wednesday 14th September 2022 | week 9 | -| *v1.2.3 released* | Monday 10th October 2022 | week 13 | -| *v1.2.4 released* | Monday 17th October 2022 | week 14 | +| *v1.2.x released* | Monday 15th August 2022 | week 5 | +| *v1.2.x released* | Wednesday 14th September 2022 | week 9 | +| *v1.2.x released* | Monday 10th October 2022 | week 13 | +| *v1.2.x released* | Monday 17th October 2022 | week 14 | | v1.3.0-beta.0 released | Tuesday 1st November 2022 | week 16 | | v1.3.0-beta.1 released | Tuesday 8th November 2022 | week 17 | -| *v1.2.5 released* | Tuesday 8th November 2022 | week 17 | +| *v1.2.x released* | Tuesday 8th November 2022 | week 17 | | release-1.3 branch created (**Begin [Code Freeze]**) | Tuesday 15th November 2022 | week 18 | | v1.3.0-rc.0 released | Tuesday 15th November 2022 | week 18 | | release-1.3 jobs created | Tuesday 15th November 2022 | week 18 | | v1.3.0-rc.1 released | Tuesday 22nd November 2022 | week 19 | | **v1.3.0 released** | Thursday 1st December 2022 | week 20 | -| *v1.2.6 released* | Thursday 1st December 2022 | week 20 | +| *v1.2.x released* | Thursday 1st December 2022 | week 20 | After the `.0` release monthly patch release will be created. diff --git a/docs/release/release-1.4.md b/docs/release/release-1.4.md index b7633107ddc4..47b7e12e090b 100644 --- a/docs/release/release-1.4.md +++ b/docs/release/release-1.4.md @@ -11,17 +11,17 @@ The following table shows the preliminary dates for the `v1.4` release cycle. | Start of Release Cycle | Release Lead | Monday 5th December 2022 | week 1 | | Schedule finalized | Release Lead | Friday 9th December 2022 | week 1 | | Team finalized | Release Lead | Friday 9th December 2022 | week 1 | -| *v1.2.7 & v1.3.1 released* | Release Lead | Tuesday 10th January 2023 | week 6 | -| *v1.2.8 & v1.3.2 released* | Release Lead | Tuesday 31st January 2023 | week 9 | +| *v1.2.x & v1.3.x released* | Release Lead | Tuesday 10th January 2023 | week 6 | +| *v1.2.x & v1.3.x released* | Release Lead | Tuesday 31st January 2023 | week 9 | | v1.4.0-beta.0 released | Release Lead | Tuesday 28th February 2023 | week 13 | -| *v1.2.9 & v1.3.3 released* | Release Lead | Tuesday 28th February 2023 | week 13 | +| *v1.2.x & v1.3.x released* | Release Lead | Tuesday 28th February 2023 | week 13 | | v1.4.0-beta.1 released | Release Lead | Tuesday 7th March 2023 | week 14 | | release-1.4 branch created (**Begin [Code Freeze]**) | Release Lead | Tuesday 14th March 2023 | week 15 | | v1.4.0-rc.0 released | Release Lead | Tuesday 14th March 2023 | week 15 | | release-1.4 jobs created | CI Manager | Tuesday 14th March 2023 | week 15 | | v1.4.0-rc.1 released | Release Lead | Tuesday 21st March 2023 | week 16 | | **v1.4.0 released** | Release Lead | Tuesday 28th March 2023 | week 17 | -| *v1.2.10 & v1.3.4 released* | Release Lead | Tuesday 28th March 2023 | week 17 | +| *v1.2.x & v1.3.x released* | Release Lead | Tuesday 28th March 2023 | week 17 | | Organize release retrospective | Release Lead | TBC | week 17 | After the `.0` release monthly patch release will be created. diff --git a/docs/release/release-tasks.md b/docs/release/release-tasks.md index d4c259d9cabb..f34e3eadc6fb 100644 --- a/docs/release/release-tasks.md +++ b/docs/release/release-tasks.md @@ -226,7 +226,8 @@ Additional information: #### [Optional] [Track] Bump the Kubernetes version -TODO(sbueringer): Follow-up PR (this will probably just be create an issue based on another issue template) +1. Create an issue for the new Kubernetes version via: [New Issue: Kubernetes bump](https://github.com/kubernetes-sigs/cluster-api/issues/new/choose). +2. Track the issue to ensure the work is completed in time. ## Communications/Docs/Release Notes Manager