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: docs/release-procedure.md
+28-4Lines changed: 28 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,13 +16,13 @@ critical bug fixes.
16
16
2. Update the minor version with the expected version.
17
17
18
18
Make changes in the `docs/manifests/tests/examples` directories using the
19
-
`hack/bump_release.sh` script by running the following command:
19
+
`hack/bump-release.sh` script by running the following command:
20
20
21
21
```bash
22
22
$ hack/bump-release.sh 28 29 0
23
23
```
24
24
25
-
This will replace `1.28.x`/`2.28.x` with `1.29.0`/`2.29.0` strings in the
25
+
This will replace `1.28.x` with `1.29.0` strings in the
26
26
`docs/manifests/tests/examples` directories. Ensure that you double-check the
27
27
diff before committing the changes. Non-related changes must not be shipped.
28
28
@@ -43,8 +43,32 @@ critical bug fixes.
43
43
44
44
6. Make PR modifying [images.yaml](https://github.com/kubernetes/k8s.io/blob/main/registry.k8s.io/images/k8s-staging-provider-os/images.yaml) to promote gcr.io images to registry.k8s.io. The point is to copy the proper image sha256 hashes from the staging repository to the images.yaml.
45
45
46
-
7. Once images are promoted create release notes using the "Generate release notes" button in the GitHub "New release" UI and publish the release.
46
+
Use `hack/release-image-digests.sh` script and `hack/verify-image-digests.sh` to verify the digests before submitting the PR.
Generate a PR with the updated `images.yaml` file. Make sure to review the changes and ensure that the correct images are being promoted.
53
+
54
+
7. Once images are promoted (takes about 30 minutes) create release notes using the "Generate release notes" button in the GitHub "New release" UI and publish the release.
55
+
56
+
8. Update the helm chart version with the expected version.
57
+
58
+
Make changes in the `charts` directory using the
59
+
`hack/bump-release.sh` script by running the following command:
60
+
61
+
```bash
62
+
$ hack/bump-charts.sh 28 29 0
63
+
```
64
+
65
+
This will replace `1.28.x`/`2.28.x` with `1.29.0`/`2.29.0` strings in the
66
+
`docs/manifests/tests/examples` directories. Ensure that you double-check the
67
+
diff before committing the changes. Non-related changes must not be shipped.
68
+
69
+
Make a PR to bump the chart version in the `charts` directory. Once the PR is
70
+
merged, the chart will be automatically published to the repository registry.
47
71
48
-
8. Update `kubernetes/test-infra` to add jobsforthe new release branchin the [`config/jobs/kubernetes/cloud-provider-openstack`](https://github.com/kubernetes/test-infra/tree/master/config/jobs/kubernetes/cloud-provider-openstack) directory.
72
+
9. Update `kubernetes/test-infra` to add jobsforthe new release branchin the [`config/jobs/kubernetes/cloud-provider-openstack`](https://github.com/kubernetes/test-infra/tree/master/config/jobs/kubernetes/cloud-provider-openstack) directory.
49
73
50
74
This is generally as simple as copying the `release-master` file to `release-X.Y`, adding `--release-XY` suffixes to the job names and `testgrid-tab-name` annotations, and updating the branch specifiers.
0 commit comments