Open rawlingsj opened 8 years ago
looks like its not getting the correct IP for the host. I think I"ve a fix in fabric8 ready to release which should hopefully fix this
mind you this fix will only work if there is node with an IP address we can use to access gogs - at least it works on minikube using a local build
yeah I'm not sure if that will work on GKE as we need the loadbalancer or ingress.
I actually exceeded my external IP quota hence why fabric8-forge is using that duff hostname, if we switch to using ingress this might all just work OOTB and no need add extra checks.
I need to test this ingress controller fix, if it works then we should be able to avoid relying on the GKE loadbalancer.. https://github.com/nginxinc/kubernetes-ingress/issues/34
sometimes on GKE the fabric8-forge pod starts before the gogs service has an external IP, this causes issues like..
Ideally it would be good to prevent the fabric8-forge pod being ready to start until the gogs service has an externally routable address using ingress or a GKE loadbalancer