Moving the release process from a github issue to markdown in the repo

This commit is contained in:
James Strong 2021-05-11 08:30:04 -04:00
parent 22f3379455
commit a27a2fed76
No known key found for this signature in database
GPG key ID: 11048BF1C893BC89

71
RELEASE.md Normal file
View file

@ -0,0 +1,71 @@
1. [nginx](https://github.com/kubernetes/ingress-nginx/tree/master/images/nginx)
* Open pull request
* Merge
* Wait for [cloud build](https://console.cloud.google.com/cloud-build/builds?project=k8s-staging-ingress-nginx)
1a. Promote images:
Open pull request to promote staging image:
[add sha - version](https://github.com/kubernetes/k8s.io/blob/main/k8s.gcr.io/images/k8s-staging-ingress-nginx/images.yaml#L1)
The sha is available in output from [cloud build](https://console.cloud.google.com/cloud-build/builds?project=k8s-staging-ingress-nginx)
2. Change to images:
* [e2e](https://github.com/kubernetes/ingress-nginx/tree/master/images/test-runner)
* [test-runner](https://github.com/kubernetes/ingress-nginx/tree/master/images/echo)
* [echo](https://github.com/kubernetes/ingress-nginx/tree/master/images/echo)
* [cfssl](https://github.com/kubernetes/ingress-nginx/tree/master/images/cfssl)
* [fastcgi-helloserver](https://github.com/kubernetes/ingress-nginx/tree/master/images/fastcgi-helloserver)
* [httpbin](https://github.com/kubernetes/ingress-nginx/tree/master/images/httpbin)
* Open pull request
* Merge
* Wait for [cloud build](https://console.cloud.google.com/cloud-build/builds?project=k8s-staging-ingress-nginx)
2a. Promote images:
* Open pull request to promote [staging image](https://github.com/kubernetes/k8s.io/blob/master/k8s.gcr.io/images/k8s-staging-ingress-nginx/images.yaml)
* e2e-test-runner
* e2e-test-cfssl
* e2e-test-echo
* e2e-test-fastcgi-helloserver
* e2e-test-httpbin
3. Update references to e2e-test-runner image:
* [e2e-image](https://github.com/kubernetes/ingress-nginx/blob/master/test/e2e-image/Dockerfile#L1)
* [run-in-docker.sh](https://github.com/kubernetes/ingress-nginx/blob/ff60aa9e2b5377db1544091b98f475a90a630297/build/run-in-docker.sh#L37)
4. Prepare for a new release:
* Change [TAG](https://github.com/kubernetes/ingress-nginx/blob/master/TAG#L1)
* Open pull request
* Merge
* [Wait for cloud build](https://console.cloud.google.com/cloud-build/builds?project=k8s-staging-ingress-nginx)
4a. Promote images:
* Open pull request to promote [staging image](https://github.com/kubernetes/k8s.io/blob/master/k8s.gcr.io/images/k8s-staging-ingress-nginx/images.yaml)
* controller
5. Release helm chart:
* Open pull request updating [Chart.yaml](https://github.com/kubernetes/ingress-nginx/blob/master/charts/ingress-nginx/Chart.yaml#L3-L4)
* Merge
* [New helm chart is available](https://github.com/kubernetes/ingress-nginx/blob/master/.github/workflows/main.yaml#L47-L68)
6. New release:
* Update static scripts:
* [generate-deploy-scripts.sh](https://github.com/kubernetes/ingress-nginx/blob/master/hack/generate-deploy-scripts.sh)
* Open pull request with the updates
* Merge
* Update changelog:
* Open pull request updating [Changelog.md](https://github.com/kubernetes/ingress-nginx/blob/master/Changelog.md)
* Merge
7. Github release