You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2018/08/16 14:48:07 UTC

[GitHub] dgrove-oss edited a comment on issue #3106: Couchdb persistency

dgrove-oss edited a comment on issue #3106: Couchdb persistency
URL: https://github.com/apache/incubator-openwhisk/pull/3106#issuecomment-413571576
 
 
   For kube deploy, we switched to using the vanilla apache/couchdb:2.1 image along with a Job using the openwhisk/kube-ansible-runner image to initialize the database.  We support three options in the kube-deploy project:
   1. a non-replicated couchdb running in the kubernetes cluster without persistent storage.
   2. a non-replicated couchdb running in the kubernetes cluster with persistent storage.
   3. using an external couchdb.  (The couchdb might actually be running in the same kubernetes cluster as OpenWhisk, but it is not deployed by the openwhisk helm chart).
   
   For travisCI, we are only testing options 1.  Our assumption is that most production deployments will probably use option 3 and configure/deploy their databases externally to the deployment of the core openwhisk system.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services