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.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,9 +41,9 @@ You must be an official maintainer of the project to be able to do a release.
41
41
- Run `scripts/releaser.sh` to create a new GitHub release. Alternatively you can create a release in the GitHub UI making sure to click on the autogenerate release node feature.
42
42
- The step above will trigger the Kubernetes based CI/CD system [Prow](https://prow.k8s.io/?repo=kubernetes-sigs%2Fexternal-dns). Verify that a new image was built and uploaded to `gcr.io/k8s-staging-external-dns/external-dns`.
43
43
- Create a PR in the [k8s.io repo](https://github.com/kubernetes/k8s.io) by taking the current staging image using the sha256 digest. They can be obtained with `scripts/get-sha256.sh`. Once the PR is merged, the image will be live with the corresponding tag specified in the PR.
44
-
- See https://github.com/kubernetes/k8s.io/pull/540 for reference
44
+
- See https://github.com/kubernetes/k8s.io/pull/8466 for reference
45
45
- Verify that the image is pullable with the given tag
46
-
-`docker run registry.k8s.io/external-dns/external-dns:v0.16.0 --version`
46
+
-`docker run registry.k8s.io/external-dns/external-dns:v0.x.0 --version`
47
47
- Branch out from the default branch and run `scripts/version-updater.sh` to update the image tag used in the kustomization.yaml and in documentation.
48
48
- Create the PR with this version change.
49
49
- Create an issue to release the corresponding Helm chart via the chart release process (below) assigned to a chart maintainer
0 commit comments