Tasks to bump to Kubernetes v1.27

[joekr]

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.
  • We will cherry-pick into release-v1.4. Which means v1.4.x and v1.5.0 will support v1.27.

Supporting managing and running on the new Kubernetes version (@furkatgofurov7)

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 (including the latest images for this kind release)
  • Verify the quickstart manually
  • Prior art: ⚠️ Use Kubernetes 1.25 in Quick Start docs and CAPD. #7156
  • bump InitWithKubernetesVersion in clusterctl_upgrade_test.go
  • PRs:
    • ⚠️ Use k8s v1.27.0 in quickstart docs and CAPD #8518
    • [release-1.4] ⚠️ Use k8s v1.27.0 in quickstart docs and CAPD #8538
• Ensure the jobs are adjusted to provide test coverage according to our support policy:
  • For the main branch and the release branch of the latest supported Cluster API minor release:
    • Add new periodic upgrade job.
    • Adjust presubmit jobs so that we have the latest upgrade jobs available on PRs.
  • For the main branch:
    • periodics & presubmits:
      • Bump KUBEBUILDER_ENVTEST_KUBERNETES_VERSION of the test-mink8s jobs to the new minimum supported management cluster version.
    • periodics:
      • Bump KUBERNETES_VERSION_MANAGEMENT of the e2e-mink8s job to the new minimum supported management cluster version.
      • Drop the oldest upgrade job as the oldest Kubernetes minor version is now out of support.
  • Prior art: Bump cluster-api jobs for v1.25/v1.26 kubernetes/test-infra#27421
  • PR: Cluster API: Bump CAPI jobs for k8s 1.27 kubernetes/test-infra#29295
• Update book:
  • Update supported versions in versions.md
    • 📖 Update versions doc with k8s v1.27 notes #8520
    • [release-1.4] 📖 Update versions doc with k8s v1.27 notes #8539
  • Update job documentation in jobs.md
    • 📖 Update jobs.md with new k8s v1.27 jobs notes #8521
    • [release-1.4] 📖 Update jobs.md with new k8s v1.27 jobs notes #8537
  • Prior art: 🌱 Update versions doc adding Kubernetes 1.25 #7194 📖 docs update jobs.md #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 (@Prajyot-Parab)

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: Upgrade cluster-api kubekins-e2e version (v20220829-d5650c79bf-1.24 -… kubernetes/test-infra#27311
  • Prior art: periodic jobs: Upgrade cluster-api kubekins-e2e version for periodics-main (v2022082… kubernetes/test-infra#27326
  • presubmit jobs PR: Upgrade cluster-api kubekins-e2e version for persubmits-main (v20230406-23cb1879e3-1.26 - v20230406-23cb1879e3-1.27) kubernetes/test-infra#29313
  • periodic jobs PR: Upgrade cluster-api kubekins-e2e version for periodics-main (v20230406-23cb1879e3-1.26 - v20230406-23cb1879e3-1.27) kubernetes/test-infra#29314
• 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: hack/ensure-go.sh, .golangci.yml, cloudbuild*.yaml, go.mod, Makefile, netlify.toml, Tiltfile
  • Prior art: 🌱 Upgrade golang version (1.18.3 -> 1.19.0) #7135
  • PR: 🌱Upgrade golang version (1.19.6 -> 1.20.3) #8527
• Bump controller-runtime (@sbueringer)
  • PR: ⚠️ Bump to CR v0.15.0 #8007
• Bump controller-tools
  • PR: 🌱 Bump controller-tools to v0.12 #8581
• 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.
  • Prior art: 🌱 Update kubebuilder envtest (1.24.2 -> 1.25.0) #7193
  • PR: 🌱Update kubebuilder envtest (1.26.0 -> 1.27.1) #8599
• Bump conversion-gen via CONVERSION_GEN_VER in Makefile
  • Prior art: 🌱 Update conversion-gen version (v0.23.1 -> v0.25.0) #7118
  • PR: 🌱Bump gcb-docker-gcloud image #8570

[killianmuldoon]

/triage accepted

[furkatgofurov7]

I can take care of it, once v1.27 is out (which is scheduled on Tuesday 11th April 2023)

/assign

[killianmuldoon]

IMO we shouldn't assign this issue as a whole - given there's a bunch of separate parts it might make it tougher to keep track of. @furkatgofurov7 - do you want to take the first section i.e. all points under Supporting managing and running on the new Kubernetes version which can be done on release?

[furkatgofurov7]

@killianmuldoon thanks sure, I did not think of a possible complication, let's break it down then into parts and work on them separately.

[killianmuldoon]

Thanks @furkatgofurov7! Just want to make sure we don't miss stuff as it comes up 🙂

[Prajyot-Parab]

@joekr I can take care of, Using new Kubernetes dependencies section.

[furkatgofurov7]

@Prajyot-Parab hey, I am planning to work on the first section Supporting managing and running on the new Kubernetes version items, and you are welcome to pick the whole second section (Using new Kubernetes dependencies) you mentioned already.

[furkatgofurov7]

/assign @Prajyot-Parab (for section 2)

[furkatgofurov7]

FYI, kubernetes v1.27 is live now and we can start working on this issue.

[sbueringer]

Please (also) assign me for reviews of the PRs (on the PRs) outside of the core CAPI repository (probably only test-infra). I'll see the PRs in core CAPI anyway, but I would also like to review the ones in test-infra.

[sbueringer]

Ideally we have someone who ensures the umbrella issue (aka the top-level issue description) is always up-to-date, by linking the opened PRs and checking the completed tasks. (this also includes verifying that we cherry-pick everything into the appropriate branches)

Based on permissions this can only be done by either @joekr or one of the CAPI maintainers (because only they have write access to the issue description). I can help out there, except someone else wants to.