Tasks to bump to Kubernetes v1.30

[sbueringer]

This issue is tracking the tasks that should be implemented after the Kubernetes minor release has been released.

Tasks

Note: 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.

• Continuously modify CAPD to use early versions of the upcoming Kubernetes release (betas and rcs):

  • Bump the Kubernetes version in test/* except for test/infrastructure/kind/*.
  • ✨ test: Bump Kubernetes version used for testing to v1.30.0-rc.1 #10384

• Modify CAPD to use the new Kubernetes release after it is GA:

  • Bump the Kubernetes version in test/* except for test/infrastructure/kind/*.
  • PR: 🌱 Bump Kubernetes in tests to v1.30.0 and claim support for v1.30 #10454
  • Prior art: TODO (previously ✨ v1.28: Prepare quickstart, capd and tests for the new release including kind bump #9160)

• Ensure the jobs are adjusted to provide test coverage according to our support policy:

  • PR: CAPI: adjust jobs due to v1.30 GA kubernetes/test-infra#32456

  • At the .versions section in the cluster-api-prowjob-gen.yaml file in test-infra:

    • Add a new entry for the new Kubernetes version
    • Adjust the released Kubernetes's version entry to refer stable-1.<minor> instead of ci/latest-1.<minor>
    • Check and update the versions for the keys etcd and coreDNS if necessary:
      • For etcd, see the DefaultEtcdVersion kubeadm constant: e.g. for v1.28.0
      • For coredns, see the CoreDNSVersion kubeadm constant:e.g. for v1.28.0

  • For the .branches.main section in the cluster-api-prowjob-gen.yaml file in test-infra:

    • For the .upgrades section:
      • Drop the oldest upgrade
      • Add a new upgrade entry from the previous to the new Kubernetes version
    • Bump the version set at .kubernetesVersionManagement to the new minimum supported management cluster version (This is the image version available as kind image).
    • Bump the version set at .kubebuilderEnvtestKubernetesVersion to the new minimum supported management cluster version.

  • Run make generate-test-infra-prowjobs to generate the resulting prowjob configuration:

    TEST_INFRA_DIR=../../k8s.io/test-infra make generate-test-infra-prowjobs

• Update book:

  • Update supported versions in versions.md
  • PR: 🌱 Bump Kubernetes in tests to v1.30.0 and claim support for v1.30 #10454
  • Prior art: 📖 book: Update versions doc adding Kubernetes 1.28 + prowjob documentation #9161

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

Bump quickstart and kind image references in CAPD

Prerequisites:

• The target Kubernetes version is GA

• There is a new kind version with/or a new set of kind images for the target Kubernetes version

• Bump quickstart and kind image references in CAPD:

  • Bump the Kubernetes version in:
    • docs/*
    • Tiltfile
  • Bump kind image references in CAPD (and also kind if necessary, including the latest images for this kind release)
    • Add new images in the kind mapper.go.
      • See the kind releases page for the list of released images.
    • Set new default image for the test framework
    • If code changes are required for CAPD to incorporate the new Kind version, update kind latestMode
  • Verify the quickstart manually
  • Prior art: TODO (previously ✨ v1.28: Prepare quickstart, capd and tests for the new release including kind bump #9160 and 🌱 bump kind version to v0.22.0 #10094)

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 via the configuration file and by running make generate-test-infra-prowjobs.
  • 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
• 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
  • PR: 🌱 Bump Go to v1.22.2 #10452
  • Prior art: 🌱 Upgrade golang version (1.18.3 -> 1.19.0) #7135
• Bump controller-runtime
  • PR: 🌱 Bump controller-runtime to v0.18.0 #10383
• Bump controller-tools
  • PR: 🌱 Bump controller-gen to v0.15 #10380
• 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.
  • PR to release envtest 1.30 binaries: ✨ Bump envtest to 1.30 kubebuilder#3864
  • PRs: 🌱 Bump envtest to v1.30.0 #10477 [release-1.7] 🌱 Bump envtest to v1.30.0 #10481
  • Prior art: 🌱 Update kubebuilder envtest (1.24.2 -> 1.25.0) #7193
• Bump conversion-gen via CONVERSION_GEN_VER in Makefile
  • PR: 🌱 Bump conversion-gen to v0.30.0 #10474
  • Prior art: 🌱 Update conversion-gen version (v0.23.1 -> v0.25.0) #7118

[sbueringer]

/assign
/triage accepted

[fabriziopandini]

/area dependency

[chrischdi]

• Update our Prow jobs for the main branch to use the correct kubekins-e2e image via the configuration file and by running make generate-test-infra-prowjobs.
  • cluster-api: Bump kubekins image for main to 1.30 to use go 1.22 kubernetes/test-infra#32380

[sbueringer]

@chrischdi Let's rewrite the issue description & template once we have consensus on how we want to change the process (e.g. multi-step bump towards a new Kubernetes version)

[chrischdi]

/kind feature

[fabriziopandini]

/priority important-soon

[sbueringer]

kind was just released so I think we can now complete "Bump quickstart and kind image references in CAPD"

[chrischdi]

I will take that over :-)