RELEASE.md

1. NGINX

• Open pull request

If you are updating any component in build.sh please also update the SHA256 checksum of that component as well, the cloud build will fail with an exit 10 if not.
Example NGINX_VERSION, SHA256

• Merge
• Wait for cloud build

1a. Promote images:

Open pull request to promote staging image: add sha - version

The sha is available in output from cloud build

2. Change to images:

• e2e

  • test-runner
  • echo
  • cfssl
  • fastcgi-helloserver
  • httpbin

• Open pull request

• Merge

• Wait for cloud build

2a. Promote images:

• Open pull request to promote staging image
  • 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
• run-in-docker.sh

4. Prepare for a new release:

• Change TAG
• Open pull request
• Merge
• Wait for cloud build

4a. Promote images:

• Open pull request to promote staging image
  • controller

5. Release helm chart:

• Open pull request updating Chart.yaml
• Merge
• New helm chart is available

6. New release:

• Update static scripts:

  • generate-deploy-scripts.sh
  • Open pull request with the updates
  • Merge

• Update Changelog and Documentation:

  • Open pull request updating Changelog.md
  • Update the version in docs/deploy/index.md
  • Update Supported versions in the Support Versions table in the README.md
  • Merge

• Update the stable.txt file to reflect the release to be created

7. Github release