You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/installing-workflow/configuring-object-storage.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ The helm classic chart for Deis Workflow can be easily configured to connect Wor
17
17
* Note: Depending on your chosen object storage you may need to provide globally unique bucket names.
18
18
* Note: If you provide credentials with sufficient access to the underlying storage, Workflow components will create the buckets if they do not exist.
19
19
***Step 2:** If applicable, generate credentials that have write access to the storage buckets created in Step 1
20
-
***Step 3:** If you haven't already fetched the helm classic chart, do so with `helmc fetch deis/workflow-v2.0.0`
20
+
***Step 3:** If you haven't already fetched the helm classic chart, do so with `helmc fetch deis/workflow-v2.1.0`
21
21
***Step 4:** Update storage details either by setting the appropriate environment variables or by modifying the template file `tpl/generate_params.toml`
22
22
***1.** Using environment variables:
23
23
* Set `STORAGE_TYPE` to `s3`, `azure` or `gcs`, then set the following environment variables accordingly.
@@ -41,14 +41,14 @@ The helm classic chart for Deis Workflow can be easily configured to connect Wor
41
41
```
42
42
43
43
***2.** Using template file `tpl/generate_params.toml`:
44
-
* Open the helm classic chart with `helmc edit workflow-v2.0.0` and look for the template file `tpl/generate_params.toml`
44
+
* Open the helm classic chart with `helmc edit workflow-v2.1.0` and look for the template file `tpl/generate_params.toml`
45
45
* Update the `storage` parameter to reference the storage platform you are using: `s3`, `azure`, `gcs`
46
46
* Update the values in the section which corresponds to your storage type, including region, bucket names and access credentials
47
47
* Note: you do not need to base64 encode any of these values as Helm Classic will handle encoding automatically
48
-
***Step 5:** Save your changes and re-generate the helm classic chart by running `helmc generate -x manifests workflow-v2.0.0`
48
+
***Step 5:** Save your changes and re-generate the helm classic chart by running `helmc generate -x manifests workflow-v2.1.0`
49
49
***Step 6:** Check the generated file in your manifests directory, you should see `deis-objectstorage-secret.yaml`
50
50
51
-
You are now ready to `helmc install workflow-v2.0.0` using your desired object storage.
51
+
You are now ready to `helmc install workflow-v2.1.0` using your desired object storage.
0 commit comments