-
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.30 #10026
Labels
area/dependency
Issues or PRs related to dependency changes
kind/feature
Categorizes issue or PR as related to a new feature.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Comments
k8s-ci-robot
added
the
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
label
Jan 19, 2024
/assign |
k8s-ci-robot
added
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
and removed
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
Jan 19, 2024
/area dependency |
k8s-ci-robot
added
the
area/dependency
Issues or PRs related to dependency changes
label
Jan 19, 2024
|
This was referenced Apr 9, 2024
@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) |
/kind feature |
k8s-ci-robot
added
the
kind/feature
Categorizes issue or PR as related to a new feature.
label
Apr 10, 2024
/priority important-soon |
k8s-ci-robot
added
the
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
label
Apr 11, 2024
This was referenced Apr 17, 2024
Merged
This was referenced Apr 22, 2024
kind was just released so I think we can now complete "Bump quickstart and kind image references in CAPD" |
I will take that over :-) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/dependency
Issues or PRs related to dependency changes
kind/feature
Categorizes issue or PR as related to a new feature.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
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):
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.30 GA kubernetes/test-infra#32456
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: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
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 the correctkubekins-e2e
image via the configuration file and by runningmake generate-test-infra-prowjobs
.hack/ensure-go.sh
,.golangci.yml
,cloudbuild*.yaml
,go.mod
,Makefile
,netlify.toml
,Tiltfile
KUBEBUILDER_ENVTEST_KUBERNETES_VERSION
inMakefile
releases and is not strictly necessary for Supporting managing and running on the new Kubernetes version.
CONVERSION_GEN_VER
inMakefile
The text was updated successfully, but these errors were encountered: