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.2.0`
20
+
***Step 3:** If you haven't already fetched the helm classic chart, do so with `helmc fetch deis/workflow-v2.3.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.
@@ -48,14 +48,14 @@ The helm classic chart for Deis Workflow can be easily configured to connect Wor
48
48
* To specify tenant set `SWIFT_TENANT` if the auth version is 2 or more.
49
49
50
50
***2.** Using template file `tpl/generate_params.toml`:
51
-
* Open the helm classic chart with `helmc edit workflow-v2.2.0` and look for the template file `tpl/generate_params.toml`
51
+
* Open the helm classic chart with `helmc edit workflow-v2.3.0` and look for the template file `tpl/generate_params.toml`
52
52
* Update the `storage` parameter to reference the storage platform you are using: `s3`, `azure`, `gcs`
53
53
* Update the values in the section which corresponds to your storage type, including region, bucket names and access credentials
54
54
* Note: you do not need to base64 encode any of these values as Helm Classic will handle encoding automatically
55
-
***Step 5:** Save your changes and re-generate the helm classic chart by running `helmc generate -x manifests workflow-v2.2.0`
55
+
***Step 5:** Save your changes and re-generate the helm classic chart by running `helmc generate -x manifests workflow-v2.3.0`
56
56
***Step 6:** Check the generated file in your manifests directory, you should see `deis-objectstorage-secret.yaml`
57
57
58
-
You are now ready to `helmc install workflow-v2.2.0` using your desired object storage.
58
+
You are now ready to `helmc install workflow-v2.3.0` using your desired object storage.
Copy file name to clipboardExpand all lines: src/installing-workflow/configuring-postgres.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
@@ -31,7 +31,7 @@ $ psql -h <host> -p <port> -d postgres -U <"postgres" or your own username>
31
31
32
32
The Helm Classic chart for Deis Workflow can be easily configured to connect the Workflow controller component to an off-cluster PostgreSQL database.
33
33
34
-
***Step 1:** If you haven't already fetched the Helm Classic chart, do so with `helmc fetch deis/workflow-v2.2.0`
34
+
***Step 1:** If you haven't already fetched the Helm Classic chart, do so with `helmc fetch deis/workflow-v2.3.0`
35
35
***Step 2:** Update database connection details either by setting the appropriate environment variables _or_ by modifying the template file `tpl/generate_params.toml`. Note that environment variables take precedence over settings in `tpl/generate_params.toml`.
36
36
***1.** Using environment variables:
37
37
* Set `DATABASE_LOCATION` to `off-cluster`.
@@ -41,18 +41,18 @@ The Helm Classic chart for Deis Workflow can be easily configured to connect the
41
41
* Set `DATABASE_USERNAME` to the username of the database user that owns the database-- typically `deis`.
42
42
* Set `DATABASE_PASSWORD` to the password for the database user that owns the database.
43
43
***2.** Using template file `tpl/generate_params.toml`:
44
-
* Open the Helm Classic chart with `helmc edit workflow-v2.2.0` and look for the template file `tpl/generate_params.toml`
44
+
* Open the Helm Classic chart with `helmc edit workflow-v2.3.0` and look for the template file `tpl/generate_params.toml`
45
45
* Update the `database_location` parameter to `off-cluster`.
46
46
* Update the values in the `[database]` configuration section to properly reflect all connection details.
47
47
* Save your changes.
48
48
* Note: Whether using environment variables or `tpl/generate_params.toml`, you do not need to (and must not) base64 encode any values, as the Helm Classic chart will automatically handle encoding as necessary.
49
-
***Step 3:** Re-generate the Helm Classic chart by running `helmc generate -x manifests workflow-v2.2.0`
49
+
***Step 3:** Re-generate the Helm Classic chart by running `helmc generate -x manifests workflow-v2.3.0`
50
50
***Step 4:** Check the generated files in your `manifests` directory. You should see:
*`deis-database-secret-creds.yaml` exists and contains base64 encoded database username and password.
53
53
* No other database-related Kubernetes resources are defined. i.e. none of `database-database-service-account.yaml`, `database-database-service.yaml`, or `database-database-rc.yaml` exist.
54
54
55
-
You are now ready to `helmc install workflow-v2.2.0`[as usual][installing].
55
+
You are now ready to `helmc install workflow-v2.3.0`[as usual][installing].
Copy file name to clipboardExpand all lines: src/managing-workflow/platform-logging.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ Error: There are currently no log messages. Please check the following things:
54
54
## Default Configuration
55
55
By default the Fluentd pod can be configured to talk to numerous syslog endpoints. So for example it is possible to have Fluentd send log messages to both the Logger component and [Papertrail](https://papertrailapp.com/). This allows production deployments of Deis to satisfy stringent logging requirements such as offsite backups of log data.
56
56
57
-
Configuring Fluentd to talk to multiple syslog endpoints means adding the following stanzas to the [Fluentd daemonset manifest](https://github.com/deis/charts/blob/master/workflow-v2.2.0/tpl/deis-logger-fluentd-daemon.yaml) -
57
+
Configuring Fluentd to talk to multiple syslog endpoints means adding the following stanzas to the [Fluentd daemonset manifest](https://github.com/deis/charts/blob/master/workflow-v2.3.0/tpl/deis-logger-fluentd-daemon.yaml) -
0 commit comments