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
This documents describes release process for the Cluster API Operator.
4
+
5
+
1. Cut the release branch.
6
+
7
+
```bash
8
+
export RELEASE_TAG=v0.1.1
9
+
10
+
git tag -s -a ${RELEASE_TAG} -m ${RELEASE_TAG}
11
+
12
+
git push upstream ${RELEASE_TAG}
13
+
```
14
+
15
+
This will trigger [release github action](https://github.com/kubernetes-sigs/cluster-api-operator/blob/main/.github/workflows/release.yaml) that will
16
+
create a draft release with operator components and helm chart, also a Prow job to publish operator image to the staging registry will start.
17
+
18
+
2. Wait for image to appear in the [staging registry](https://console.cloud.google.com/gcr/images/k8s-staging-capi-operator/global/cluster-api-operator).
19
+
20
+
3. Create a GitHub [Personal access tokens](https://github.com/settings/tokens) if you don't have one already. We're going to use for opening a PR
21
+
to promote image from staging to production.
22
+
23
+
```bash
24
+
export GITHUB_TOKEN=<your GH token>
25
+
make promote-images
26
+
```
27
+
28
+
Merge the PR after it was created and verify that image is present in the production registry.
0 commit comments