Skip to content

1.1.0-gcm.8

Choose a tag to compare

@maelvls maelvls released this 30 Mar 20:18
· 83 commits to main since this release

For fresh installs, install 1.1.0-gcm.9 instead (breaking change in CRD validation).

The versions 1.1 and 1.3 are deprecated since 24 June 2021 and will be removed on 14 January 2022. We invite users to upgrade to the latest version of the application.

Changelog

  • The preflight deployment is now "green" after a fresh click-to-deploy. Initially, we thought that it would make sense to leave the preflight deployment fail on a fresh install in order to "indicate" that an action was needed to set up http://platform.jetstack.io/, but we later realized that it led to a poor UX. (#41)
    Before/after:
    The test-1 application page on GKE should show the test-1 application. The preflight deployment is failing because the user has not (yet) gone to http://platform.jetstack.io/ to register their cluster. This screenshot is stored in this issue: https://github.com/jetstack/jetstack-secure-gcm/issues/21 The application page for test-1 shows that all the deployments are green. This screenshot is stored in this issue: https://github.com/jetstack/jetstack-secure-gcm/issues/21

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.8
git tag 1.1.0-gcm.8
commit 405c4f8
logs https://console.cloud.google.com/cloud-build/builds/29685ce7-b998-4078-9611-e509f5b086e6?project=885059085598

Step-by-step process followed:

  • Update the above table with the correct information (the logs link is
    available after running gcloud builds below).

  • Retag all images with the new tag. We do this because we do not have
    automated the "rebuild of images with the LICENSES file embedded", which
    will be done in #10.
    So we have to use an existing prior tag and retag every image to the new
    tag:

    V=1.1.0-gcm.8
    EXISTING_V=1.1.0-gcm.1
    retag() { # Usage: retag FROM_IMAGE_WITH_TAG TO_IMAGE_WITH_TAG
      local FROM=$1 TO=$2
      docker pull $FROM && docker tag $FROM $TO && docker push $TO
    }
    retagall() { # Usage: retagall FROM_REGISTRY FROM_TAG TO_REGISTRY TO_TAG
      local FROM=$1 TO=$2 FROM_TAG=$3 TO_TAG=$4
      retag $FROM:$FROM_TAG $TO:$TO_TAG || exit 1
      retag $FROM/cert-manager-acmesolver:$FROM_TAG $TO/cert-manager-acmesolver:$TO_TAG || exit 1
      retag $FROM/cert-manager-cainjector:$FROM_TAG $TO/cert-manager-cainjector:$TO_TAG || exit 1
      retag $FROM/cert-manager-webhook:$FROM_TAG $TO/cert-manager-webhook:$TO_TAG || exit 1
      retag $FROM/cert-manager-google-cas-issuer:$FROM_TAG $TO/cert-manager-google-cas-issuer:$TO_TAG || exit 1
      retag $FROM/preflight:$FROM_TAG $TO/preflight:$TO_TAG || exit 1
      retag gcr.io/cloud-marketplace-tools/metering/ubbagent:latest $TO/ubbagent:$TO_TAG || exit 1
    }
    retagall gcr.io/jetstack-public/jetstack-secure-for-cert-manager{,} $EXISTING_V $V
  • Bump the version number in
    schema.yaml.

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

  • Run a build to create the deployer image:

    V=1.1.0-gcm.8
    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
  • Tag the commit that was used to run gcloud builds submit:

    V=1.1.0-gcm.8
    COMMIT=405c4f890d1c5631df7ee6be88c1b4d6addf1837
    git tag $V $COMMIT
    git push --tags
  • Go to the GitHub Releases and edit the tag and add this current Markdown <details> block _+ the release notes to the tag and release it. Update any instructions that you had to tweak in order to make this release.

  • 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):
    To update the already released minor version, first open the existing minor version by clicking on the version itself (it is a link). This screenshot is stored in this issue: https://github.com/jetstack/jetstack-secure-gcm/issues/21 Then, click on Update images and Save. This screenshot is stored in this issue: https://github.com/jetstack/jetstack-secure-gcm/issues/21 The solution admin page has a button 'Submit for review' at the bottom that must be clicked in order to get the new version reviewed by Google. This screenshot is stored in this issue: https://github.com/jetstack/jetstack-secure-gcm/issues/21