advancedtelematic / ota-community-edition

End-to-end Over The Air updates
Mozilla Public License 2.0
54 stars 23 forks source link

make print-hosts does not output IP addresses #79

Closed marceleng closed 6 years ago

marceleng commented 6 years ago

My setup:

After successful start of the cluster, make print-hosts doesn't output any IP address:

# sudo make print-hosts
80 app.ota.local
80 gateway.ota.local
80 treehub.ota.local
80 tuf-reposerver.ota.local
80 web-events.ota.local
# sudo kubectl get ingress
NAME             HOSTS                      ADDRESS   PORTS     AGE
app              app.ota.local                        80        1h
gateway          gateway.ota.local                    80        1h
treehub          treehub.ota.local                    80        1h
tuf-reposerver   tuf-reposerver.ota.local             80        1h
web-events       web-events.ota.local                 80        1h
# sudo kubectl get services --all-namespaces
NAMESPACE       NAME                   TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                                     AGE
default         app                    ClusterIP   10.107.3.152     <none>        80/TCP                                      1h
default         campaigner             ClusterIP   10.102.164.178   <none>        80/TCP                                      1h
default         crypt-vault            ClusterIP   10.96.70.153     <none>        80/TCP                                      1h
default         device-registry        ClusterIP   10.101.167.1     <none>        80/TCP                                      1h
default         director               ClusterIP   10.100.20.143    <none>        80/TCP                                      1h
default         gateway-service        ClusterIP   10.106.84.190    <none>        8000/TCP                                    1h
default         kafka                  ClusterIP   10.102.28.135    <none>        9092/TCP                                    1h
default         kubernetes             ClusterIP   10.96.0.1        <none>        443/TCP                                     1h
default         mysql                  ClusterIP   10.98.236.23     <none>        3306/TCP                                    1h
default         treehub                ClusterIP   10.111.165.54    <none>        80/TCP                                      1h
default         tuf-keyserver          ClusterIP   10.99.66.66      <none>        80/TCP                                      1h
default         tuf-keyserver-daemon   ClusterIP   10.104.7.68      <none>        80/TCP                                      1h
default         tuf-reposerver         ClusterIP   10.102.197.51    <none>        80/TCP                                      1h
default         tuf-vault              ClusterIP   10.110.139.80    <none>        80/TCP                                      1h
default         web-events             ClusterIP   10.98.220.191    <none>        80/TCP                                      1h
default         zookeeper              ClusterIP   10.104.78.52     <none>        2181/TCP,2888/TCP,3888/TCP                  1h
ingress-nginx   default-http-backend   ClusterIP   10.98.31.204     <none>        80/TCP                                      1h
ingress-nginx   ingress-nginx          NodePort    10.101.187.212   <none>        8000:31663/TCP,80:32711/TCP,443:32138/TCP   1h
kube-system     kube-dns               ClusterIP   10.96.0.10       <none>        53/UDP,53/TCP                               1h
kube-system     kubernetes-dashboard   NodePort    10.96.35.213     <none>        80:30000/TCP                                1h

I've looked a bit at this issue but the mentionned workaround does not seem to work for me.

taheris commented 6 years ago

Which commit are you using? A merge was created yesterday from PR #77 to use the minikube ip instead which should be more reliable (when using minikube anyway).

marceleng commented 6 years ago

My bad, I did not see that commit. Everything works for me after pulling the latest tree :)

Thanks!