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/04/13 05:07:09 UTC

[GitHub] pulasthi opened a new issue #180: accessing the couchdb instance separately

pulasthi opened a new issue #180: accessing the couchdb instance separately 
URL: https://github.com/apache/incubator-openwhisk-deploy-kube/issues/180
 
 
   Hi Devs,
   
   I have a openwhisk cluster deployed, and for my application, I want to access the internal couchDB database 1. From within the function and 2. From an external location. I have added the svc list below
   
   `NAME         TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                                                    AGE
   apigateway   NodePort    10.102.34.138    <none>        8080:31305/TCP,9000:31295/TCP                              7h
   controller   ClusterIP   10.104.235.255   <none>        8080/TCP                                                   7h
   couchdb      NodePort    10.100.59.247    <none>        5984:30641/TCP                                             4h
   kafka        ClusterIP   10.99.132.46     <none>        9092/TCP                                                   7h
   nginx        NodePort    10.104.182.149   <none>        5984:31064/TCP,80:32641/TCP,443:31141/TCP,8443:31389/TCP   3m
   zookeeper    ClusterIP   10.102.198.186   <none>        2181/TCP,2888/TCP,3888/TCP                                 7h
   `
   
   I tried several things but i can't seem to access the couchDB database. I changed the couchDB service from ClusterIp to NodePort. Any help with the following will be greatly appreciated. Lets assume the ip of the mode is 123.45.67.89
   
   1. What host:port to use from with the a function? i thought it would be 123.45.67.89:30641 but it didn't work, 
   
   2. What host:port to use from the out side (like a curl call)?
   
   Best Regards,
   Pulasthi

----------------------------------------------------------------
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