jpchev edited a comment on issue #678: URL: https://github.com/apache/openwhisk-deploy-kube/issues/678#issuecomment-792620700
from a bash inside the couch init pod, the following command (correponding to `curl --output /dev/null --silent $DB_PROTOCOL://$DB_HOST:$DB_PORT/_utils`) hangs `curl --output /dev/null http://owdev-couchdb.openwhisk.svc.cluster.local:5984/_utils` whereas the same command, using the IP of the couchdb pod works `curl --output /dev/null http://10.44.0.4:5984/_utils` So it seems the IP of the couchdb service (which corresponds to owdev-couchdb.openwhisk.svc.cluster.local) doesn't reach the pod behind. This seems to happen randomly, after installing openwhisk: sometimes the couchdb init pod completes (after that I have other availability problems when creating functions, but that's for another issue...). **I'm not sure, but I would say this issue doesn't happen when the couch db pod and the couch db init pod get deployed on the same Kubernetes node.** I've checked rules in iptables for the couchdb services, it seems the routing is in place: ``` sudo iptables-save | grep couchdb -A KUBE-SEP-SNMSYAE7RYOIOXBL -s 10.44.0.4/32 -m comment --comment "openwhisk/owdev-couchdb:couchdb" -j KUBE-MARK-MASQ -A KUBE-SEP-SNMSYAE7RYOIOXBL -p tcp -m comment --comment "openwhisk/owdev-couchdb:couchdb" -m tcp -j DNAT --to-destination 10.44.0.4:5984 -A KUBE-SERVICES ! -s 10.244.0.0/16 -d 10.99.12.131/32 -p tcp -m comment --comment "openwhisk/owdev-couchdb:couchdb cluster IP" -m tcp --dport 5984 -j KUBE-MARK-MASQ -A KUBE-SERVICES -d 10.99.12.131/32 -p tcp -m comment --comment "openwhisk/owdev-couchdb:couchdb cluster IP" -m tcp --dport 5984 -j KUBE-SVC-4DTNEZVJQQUBR77C -A KUBE-SVC-4DTNEZVJQQUBR77C -m comment --comment "openwhisk/owdev-couchdb:couchdb" -j KUBE-SEP-SNMSYAE7RYOIOXBL ``` and the endpoints are in place ``` kubectl get endpoints -n openwhisk NAME ENDPOINTS AGE owdev-apigateway 10.44.0.5:9000,10.44.0.5:8080 29m owdev-controller 29m owdev-couchdb 10.44.0.4:5984 29m owdev-kafka 10.36.0.3:9092 29m owdev-nginx 29m owdev-redis 10.36.0.1:6379 29m owdev-zookeeper 10.44.0.7:2181,10.44.0.7:2888,10.44.0.7:3888 29m ``` Do you know where to look into, to have the couchdb cluster IP service be routed to the backing pod? Do you have any idea? Thanks ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
