nikolavukovic commented on issue #577: Kafka, Controller and Invoker pods stuck in Init phase, CouchDB not initialized properly URL: https://github.com/apache/openwhisk-deploy-kube/issues/577#issuecomment-578306002 Hi David, many thanks for replying! Indeed, zookeeper is not reachable from the kafka pod container. I entered the container and tried to executed the command. This is what I get: ``` result=1; until [ $result -eq 0 ]; do OK=$(echo ruok | nc -w 1 owdev-zookeeper-0.owdev-zookeeper.openwhisk.svc.kubernetes.default.svc.cluster.local 2181); if [ "$OK" == "imok" ]; then result=0; echo "zookeeper returned imok!"; else echo waiting for zookeeper to be ready; sleep 1; fi; done; echo "Success: zookeeper is up" nc: bad address 'owdev-zookeeper-0.owdev-zookeeper.openwhisk.svc.kubernetes.default.svc.cluster.local' waiting for zookeeper to be ready nc: bad address 'owdev-zookeeper-0.owdev-zookeeper.openwhisk.svc.kubernetes.default.svc.cluster.local' ``` Another problem I had before this is that nginx pod would enter into CrashLoopBackOff state because it had a networking problem. In mycluster.yaml I had to put ``` k8s: domain: kubernetes.default.svc.cluster.local ``` instead of ``` k8s: domain: cluster.local ``` I was following another issue started here before related to networking and so I changed domain value without really being aware of the consequences. Can you explain what could be done in this case and why cluster.local was not working? Basically, this is what I get when using nslookup from nginx pod: ``` root@owdev-nginx-8495fdcb9c-88zhz:/# nslookup cluster.local Server: 10.96.0.10 Address: 10.96.0.10#53 *** Can't find cluster.local: No answer root@owdev-nginx-8495fdcb9c-88zhz:/# nslookup kubernetes.default.svc.cluster.local Server: 10.96.0.10 Address: 10.96.0.10#53 Name: kubernetes.default.svc.cluster.local Address: 10.96.0.1 ```
---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services
