Skip to content

Latest commit

 

History

History
51 lines (40 loc) · 1.54 KB

releases.md

File metadata and controls

51 lines (40 loc) · 1.54 KB

Releasing procedure

In order to release a new version of the Ambassador Operator we should:

  • Switch to the master branch 
    git co master
  • Create a new tag: 
    git tag -a v1.0
  • Push tags 
    git push --tags

This should trigger the following processes:

  • A new Ambassador Operator image will be built and pushed to quay.io and to a private repo in Azure.
  • New CRDs and Deployment manifests will be generated and published in the releases page.
  • A new version of the Helm chart will be packaged and published to the https://getambassador.io Helm repository.

Running some things manually

This section explains how to do some things manually, just in case you must release something from your laptop.

Publishing the image to the Azure registry

  • Determine the tag we will use for the image version, AMB_OPER_IMAGE_TAG.
  • Get a credentials file for Azure, as described in the credentials document.
  • Go to https://portal.azure.com/ and create a Resource Group, or use an existing one (like the default ones, like DefaultResourceGroup-EUS).
  • Run the following command: 
    AZ_RES_GRP="DefaultResourceGroup-EUS" \
CLUSTER_REGISTRY="datawire" \
CLUSTER_PROVIDER="azure" \
AZ_AUTH_FILE=<AUTHENTICATION_FILE> \
TRAVIS=true \
AMB_OPER_IMAGE_TAG=<TAG> \
make ci/publish-image-cloud