From 2211f67ef89ea4cf8464838b3f298453e11ed756 Mon Sep 17 00:00:00 2001 From: Vaughn Dice Date: Thu, 5 Jan 2017 12:45:46 -0700 Subject: [PATCH] docs(*): add upgrade note for gcs/gcr Ref https://github.com/deis/registry-token-refresher/pull/7 Ref https://github.com/deis/workflow/pull/672 --- src/managing-workflow/upgrading-workflow.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/src/managing-workflow/upgrading-workflow.md b/src/managing-workflow/upgrading-workflow.md index d48e4bf1..d2bda148 100644 --- a/src/managing-workflow/upgrading-workflow.md +++ b/src/managing-workflow/upgrading-workflow.md @@ -31,6 +31,15 @@ period of downtime while the database recovers from backup. $ helm upgrade deis/workflow ``` + +**Note:** If using off-cluster object storage on [gcs](https://cloud.google.com/storage/) and/or off-cluster registry using [gcr](https://cloud.google.com/container-registry/) and intending to upgrade from a pre-`v2.10.0` chart to `v2.10.0` or greater, the `key_json` values will now need to be pre-base64-encoded. Therefore, assuming the rest of the custom/off-cluster values are defined in the existing `values.yaml` used for previous installs, the following may be run: + +``` +$ B64_KEY_JSON="$(cat ~/path/to/key.json | base64 | tr -d '[:space:]')" +$ helm upgrade deis/workflow -f values.yaml --set gcs.key_json="${B64_KEY_JSON}",registry-token-refresher.gcr.key_json="${B64_KEY_JSON}" +$ # alternatively, simply replace the appropriate values in values.yaml and do without the `--set` parameter +``` + ### Step 2: Verify Upgrade Verify that all components have started and passed their readiness checks: