This is an automated email from the ASF dual-hosted git repository.
dgrove pushed a commit to branch master
in repository
https://gitbox.apache.org/repos/asf/incubator-openwhisk-deploy-kube.git
The following commit(s) were added to refs/heads/master by this push:
new 5419978 motivate why an external database is desirable for production
(#456)
5419978 is described below
commit 5419978436e7e498f9d243a583d94aaca6b00a50
Author: David Grove <[email protected]>
AuthorDate: Mon Apr 29 10:01:57 2019 -0400
motivate why an external database is desirable for production (#456)
---
docs/configurationChoices.md | 14 +++++++++++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/docs/configurationChoices.md b/docs/configurationChoices.md
index 4e522a5..1ca7df5 100644
--- a/docs/configurationChoices.md
+++ b/docs/configurationChoices.md
@@ -48,9 +48,17 @@ We are actively working on reducing this list and would
welcome PRs to help.
### Using an external database
You may want to use an external CouchDB or Cloudant instance instead
-of deploying a CouchDB instance as a Kubernetes pod. You can do this
-by adding a stanza like the one below to your `mycluster.yaml`,
-substituting in the appropriate values for `<...>`
+of deploying a CouchDB instance as a Kubernetes pod as part of the
+same `helm install` as the rest of OpenWhisk. Using an external
+database is especially useful in production scenarios as it decouples
+the management of the database from that of the rest of the
+system. Decoupling the database increases operational flexibility, for
+example by enabling blue/green deployments of OpenWhisk using a shared
+database instance.
+
+To use an externally deployed database, add a stanza like the one
+below to your `mycluster.yaml`, substituting in the appropriate values
+for `<...>`
```yaml
db:
external: true
