1.1.0-gcm.5

Changelog

• The billing agent was reporting much more than it should have been reporting. (#39)

Notes

📦 Recording of the manual steps of the release process

Since we do not have yet a CD pipeline that would do the work, we prefer documenting every step of the manual process on every single release in order to (1) have a record of what has been done, and (2) be able to remember how to release for the next time.

Information about this release:

deployer image	gcr.io/jetstack-public/jetstack-secure-for-cert-manager/deployer:1.1.0-gcm.5
git tag	1.1.0-gcm.5
commit	c43be00
logs	https://console.cloud.google.com/cloud-build/builds/675b5929-0f7c-446b-8854-7b38c55dec41?project=885059085598

Step-by-step process followed:

1. Bump the version number in schema.yaml and in application.yaml.

2. Copy-paste the commit you are on to the above table.

3. Make sure to be logged in with gcloud and to have the "Editor" role on the jetstack-public repo.

4. Run a build to create the deployer image:

   V=1.1.0-gcm.5
   gcloud builds submit --project jetstack-public --timeout 1800s --config cloudbuild.yaml \
     --substitutions _CLUSTER_NAME=smoke-test,_CLUSTER_LOCATION=europe-west2-b,_APP_MINOR_VERSION=$(awk 'BEGIN {FS="."}; {print $1 "." $2}' <<<$V),_APP_VERSION=$V

5. Copy-paste the logs link to the above table.

6. Tag the commit that was used to run gcloud builds submit:

   V=1.1.0-gcm.5
   COMMIT=c43be00b36f7fd1d01f15771025308b8f5ab69f7
   git tag $V $COMMIT
   git push --tags

7. Finally, go to the solution admin UI, click "Update the image" and "Save". After saving, go to the solution page and click "Submit for review" (you must be "Editor" of the jetstack-public project):