-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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 to bump to Kubernetes v1.31 #10653
Comments
/assign @sbueringer /triage accepted Nothing to do until ~ July. |
FYI, 1.31 beta is out now. Ref: https://github.com/kubernetes/kubernetes/releases/tag/v1.31.0-beta.0 Looking forward to help with few things here out of many. :) |
Thx! Let's see how it goes. Not sure about the critical path to get v1.31 support out, because we have a very tight deadline, so I would like to do this closely coordinated with @chrischdi. But there are a definitely other tasks on this issue that are not in the critical path (they'll be after Kubernetes 1.31 GA and CAPI v1.8.1 though) |
Hi. Can I take this task ? |
This can only be done after the prerequisites are fulfilled:
|
@sbueringer |
Hey folks,
|
kind v0.24 was released (https://github.com/kubernetes-sigs/kind/releases/tag/v0.24.0) So "Bump quickstart and kind image references in CAPD" is also unblocked |
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 (@sbueringer / @chrischdi)
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):
test/*
except fortest/infrastructure/kind/*
.Modify CAPD to use the new Kubernetes release after it is GA:
test/*
except fortest/infrastructure/kind/*
.Ensure the jobs are adjusted to provide test coverage according to our support policy:
PR: CAPI: adjust jobs due to v1.31 GA kubernetes/test-infra#33294
At the
.versions
section in thecluster-api-prowjob-gen.yaml
file in test-infra:stable-1.<minor>
instead ofci/latest-1.<minor>
etcd
andcoreDNS
if necessary:DefaultEtcdVersion
kubeadm constant: e.g. for v1.28.0CoreDNSVersion
kubeadm constant:e.g. for v1.28.0For the
.branches.main
section in thecluster-api-prowjob-gen.yaml
file in test-infra:.upgrades
section:.kubernetesVersionManagement
to the new minimum supported management cluster version (This is the image version available as kind image)..kubebuilderEnvtestKubernetesVersion
to the new minimum supported management cluster version.Run
make generate-test-infra-prowjobs
to generate the resulting prowjob configuration:Prior art: CAPI: adjust jobs due to v1.30 GA kubernetes/test-infra#32456
Update book:
versions.md
Issues specific to the Kubernetes minor release:
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:
docs/*
Tiltfile
Cherry-pick above PR to the latest release branch.
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.
main
branch to use thekubekins-e2e
with the correct Kubernetes version via cluster-api-prowjob-gen.yaml and by runningmake generate-test-infra-prowjobs
.hack/ensure-go.sh
,.golangci.yml
,cloudbuild*.yaml
,go.mod
,Makefile
,netlify.toml
,Tiltfile
CONVERSION_GEN_VER
inMakefile
KUBEBUILDER_ENVTEST_KUBERNETES_VERSION
inMakefile
Follow-ups after CR v0.19 bump:
controller
label controller-runtime#2895)workqueue_depth{pod=~"$Pod",name=~"$Controller"}
. We should keep using name there for compatibility with controllers that are using CR versions <= v0.18.xThe text was updated successfully, but these errors were encountered: