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/release-tasks.md
+10-6Lines changed: 10 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -188,6 +188,9 @@ to a newer Go minor version according to our [backport policy](./../../CONTRIBUT
188
188
1. Ensure CI is stable before cutting the release (e.g. by checking with the CI manager)
189
189
Note: special attention should be given to image scan results, so we can avoid cutting a release with CVE or document known CVEs in release notes.
190
190
2. Create and push the release tags to the GitHub repository:
191
+
192
+
**NOTE:** clusterctl will have issues installing providers between the time the release tag is cut and the Github release is published. See [issue 7889](https://github.com/kubernetes-sigs/cluster-api/issues/7889) for more details
193
+
191
194
```bash
192
195
# Export the tag of the release to be cut, e.g.:
193
196
export RELEASE_TAG=v1.0.1
@@ -216,12 +219,13 @@ to a newer Go minor version according to our [backport policy](./../../CONTRIBUT
216
219
git to use `https` instead via `git config --global url."https://github.com/".insteadOf [email protected]:`.
217
220
* This will automatically create a PR in [k8s.io](https://github.com/kubernetes/k8s.io) and assign the CAPI maintainers.
218
221
4. Merge the PR (/lgtm + /hold cancel) and verify the images are available in the production registry:
* Wait for the [promotion prow job](https://prow.k8s.io/?repo=kubernetes%2Fk8s.io&job=post-k8sio-image-promo) to complete successfully. Then test the production images are accessible:
0 commit comments