You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/kubernetes_bump.md
+36-21Lines changed: 36 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,30 +11,20 @@ This issue is tracking the tasks that should be implemented **after** the Kubern
11
11
12
12
## Tasks
13
13
14
-
Prerequisites:
15
-
*[ ] Decide which Cluster API release series will support the new Kubernetes version
16
-
* If feasible we usually cherry-pick the changes back to the latest release series.
14
+
**Note:** If feasible we usually cherry-pick the changes back to the latest release series.
17
15
18
16
### Supporting managing and running on the new Kubernetes version
19
17
20
18
This section contains tasks to update our book, e2e testing and CI to use and test the new Kubernetes version
21
19
as well as changes to Cluster API that we might have to make to support the new Kubernetes version. All of these
22
20
changes should be cherry-picked to all release series that will support the new Kubernetes version.
23
21
24
-
*[ ] Modify quickstart and CAPD to use the new Kubernetes release:
25
-
* Bump the Kubernetes version in:
26
-
*`test/*`: search for occurrences of the previous Kubernetes version
27
-
*`Tiltfile`
28
-
* Ensure the latest available kind version is used (including the latest images for this kind release)
29
-
* Add new images in the [kind mapper.go](https://github.com/kubernetes-sigs/cluster-api/blob/0f47a19e038ee6b0d3b1e7675a62cdaf84face8c/test/infrastructure/kind/mapper.go#L79).
30
-
* See the [kind releases page](https://github.com/kubernetes-sigs/kind/releases) for the list of released images.
31
-
* Set new default image for the [test framework](https://github.com/kubernetes-sigs/cluster-api/blob/0f47a19e038ee6b0d3b1e7675a62cdaf84face8c/test/framework/bootstrap/kind_provider.go#L40)
32
-
* If code changes are required for CAPD to incorporate the new Kind version, update [kind latestMode](https://github.com/kubernetes-sigs/cluster-api/blob/0f47a19e038ee6b0d3b1e7675a62cdaf84face8c/test/infrastructure/kind/mapper.go#L66)
33
-
* Prior art: #10094
34
-
* Verify the quickstart manually
35
-
* Bump `InitWithKubernetesVersion` and `WorkloadKubernetesVersion` in `clusterctl_upgrade_test.go`
36
-
* Note: Only bump for Cluster API versions that will support the new Kubernetes release.
37
-
* Prior art: #9160
22
+
*[ ] Continuously modify CAPD to use early versions of the upcoming Kubernetes release (betas and rcs):
23
+
* Bump the Kubernetes version in `test/*` except for `test/infrastructure/kind/*`.
24
+
* Prior art: #10384
25
+
*[ ] Modify CAPD to use the new Kubernetes release after it is GA:
26
+
* Bump the Kubernetes version in `test/*` except for `test/infrastructure/kind/*`.
27
+
* Prior art: #10454
38
28
*[ ] Ensure the jobs are adjusted to provide test coverage according to our [support policy](https://cluster-api.sigs.k8s.io/reference/versions.html#supported-kubernetes-versions):
39
29
40
30
* At the `.versions` section in the `cluster-api-prowjob-gen.yaml` file in [test-infra](https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes-sigs/cluster-api/):
@@ -55,13 +45,36 @@ changes should be cherry-picked to all release series that will support the new
55
45
TEST_INFRA_DIR=../../k8s.io/test-infra make generate-test-infra-prowjobs
56
46
```
57
47
48
+
* Prior art: #32456
49
+
58
50
* [ ] Update book:
59
51
* Update supported versions in`versions.md`
60
-
* Prior art: #9161
52
+
* Prior art: #10454
53
+
61
54
* [ ] Issues specific to the Kubernetes minor release:
62
55
* Sometimes there are adjustments that we have to make in Cluster API to be able to support
63
56
a new Kubernetes minor version. Please add these issues here when they are identified.
64
57
58
+
### Bump quickstart and kind image references in CAPD
59
+
60
+
Prerequisites:
61
+
62
+
* The target Kubernetes version is GA
63
+
* There is a new [kind version with/or a new set of kind images](https://github.com/kubernetes-sigs/kind/releases) for the target Kubernetes version
64
+
65
+
* [ ] Bump quickstart and kind image references in CAPD:
66
+
* Bump the Kubernetes version in:
67
+
*`docs/*`
68
+
*`Tiltfile`
69
+
* Bump kind image references in CAPD (and also kind if necessary, including the latest images for this kind release)
70
+
* Add new images in the [kind mapper.go](https://github.com/kubernetes-sigs/cluster-api/blob/0f47a19e038ee6b0d3b1e7675a62cdaf84face8c/test/infrastructure/kind/mapper.go#L79).
71
+
* See the [kind releases page](https://github.com/kubernetes-sigs/kind/releases) for the list of released images.
72
+
* Set new default image for the [test framework](https://github.com/kubernetes-sigs/cluster-api/blob/0f47a19e038ee6b0d3b1e7675a62cdaf84face8c/test/framework/bootstrap/kind_provider.go#L40)
73
+
* If code changes are required for CAPD to incorporate the new Kind version, update [kind latestMode](https://github.com/kubernetes-sigs/cluster-api/blob/0f47a19e038ee6b0d3b1e7675a62cdaf84face8c/test/infrastructure/kind/mapper.go#L66)
74
+
* Verify the quickstart manually
75
+
* Prior art: #10610
76
+
* [ ] Cherry-pick above PR to the latest release branch.
77
+
65
78
### Using new Kubernetes dependencies
66
79
67
80
This section contains tasks to update Cluster API to use the latest Kubernetes Go dependencies and related topics
@@ -72,17 +85,19 @@ run the Cluster API controllers on the new Kubernetes version.
72
85
* [ ] Ensure there is a new controller-runtime minor release which uses the new Kubernetes Go dependencies.
73
86
* [ ] 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`.
74
87
* It is recommended to have one PR for presubmit and one for periodic jobs to reduce the risk of breaking the periodic jobs.
* [ ] Bump the Go version in Cluster API: (if Kubernetes is using a new Go minor version)
78
90
* Search for the currently used Go version across the repository and update it
79
91
* We have to at least modify it in: `hack/ensure-go.sh`, `.golangci.yml`, `cloudbuild*.yaml`, `go.mod`, `Makefile`, `netlify.toml`, `Tiltfile`
80
-
* Prior art: #7135
92
+
* Prior art: #10452
81
93
* [ ] Bump controller-runtime
82
94
* [ ] Bump controller-tools
83
95
* [ ] Bump the Kubernetes version used in integration tests via `KUBEBUILDER_ENVTEST_KUBERNETES_VERSION` in `Makefile`
84
96
* **Note**: This PR should be cherry-picked as well. It is part of this section as it depends on kubebuilder/controller-runtime
85
97
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).
98
+
* Prior art to release envtest binaries: https://github.com/kubernetes-sigs/kubebuilder/pull/3864
86
99
* Prior art: #7193
87
100
* [ ] Bump conversion-gen via `CONVERSION_GEN_VER` in `Makefile`
88
101
* Prior art: #7118
102
+
103
+
After release of CAPI v1.X.x (that supports Kubernetes v1.Y):
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/release_tracking.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,4 +81,7 @@ Continuously:
81
81
If and when necessary:
82
82
*[ ][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)
83
83
*[ ][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)
84
-
*[ ][Release Lead][Track Release and Improvement tasks](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#optional-track-release-and-improvement-tasks)
84
+
*[ ][Release Lead][Track Release and Improvement tasks](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#optional-track-release-and-improvement-tasks)
<!-- Thanks for sending a pull request! Here are some tips for you:
2
+
1. If this is your first time, please read our contributor guidelines: https://github.com/kubernetes-sigs/cluster-api/blob/main/CONTRIBUTING.md#contributing-a-patch and developer guide https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/book/src/developer/guide.md
3
+
4
+
2. Please add an icon to the title of this PR (see https://sigs.k8s.io/cluster-api/CONTRIBUTING.md#contributing-a-patch), and delete this line and similar ones
5
+
the icon will be either ⚠️ (:warning:, major or breaking changes), ✨ (:sparkles:, feature additions), 🐛 (:bug:, patch and bugfixes), 📖 (:book:, documentation or proposals), or 🌱 (:seedling:, minor or other)
6
+
-->
7
+
8
+
**What this PR does / why we need it**:
9
+
10
+
**Which issue(s) this PR fixes***(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*:
11
+
Fixes #
12
+
13
+
<!--
14
+
Please label this pull request according to what area(s) you are addressing. For reference on PR/issue labels, see: https://github.com/kubernetes-sigs/cluster-api/labels?q=area+
0 commit comments