This is an automated email from the ASF dual-hosted git repository.
csantanapr 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 b6711f2 Update sample yaml snippet for external providers db (#410)
b6711f2 is described below
commit b6711f2a33b311284263fde4a4de85aeb3035660
Author: David Grove <[email protected]>
AuthorDate: Tue Jan 15 13:01:19 2019 -0500
Update sample yaml snippet for external providers db (#410)
---
docs/configurationChoices.md | 18 ++++++++----------
1 file changed, 8 insertions(+), 10 deletions(-)
diff --git a/docs/configurationChoices.md b/docs/configurationChoices.md
index 9a49947..e6de1b7 100644
--- a/docs/configurationChoices.md
+++ b/docs/configurationChoices.md
@@ -42,18 +42,16 @@ user action containers created by the
DockerContainerFactory are not configured
themselves be able to invoke Kubernetes services). To work around this you
must do one
of the following three alternatives:
1. Deploy a CouchDB instance external to your Kubernetes cluster and configure
the event
-provider(s) to use it by adding stanzas like the following to your
`mycluster.yaml`:
+providers to use it by adding a stanza like the following to your
`mycluster.yaml`:
```yaml
providers:
- alarm:
- db:
- external: true
- prefix: "alm"
- host: "0.0.0.0"
- port: 5984
- protocol: "http"
- username: "admin"
- password: "secret"
+ db:
+ external: true
+ host: "0.0.0.0"
+ port: 5984
+ protocol: "http"
+ username: "admin"
+ password: "secret"
```
2. Configure the DNS nameservers for the user containers created by
DockerContainerFactory to
use Kubernetes's DNS service. For example, if your cluster uses kube-dns,
then first
