kubeflow: installation failure because do not have external IP for istio-ingressgateway

I tried to deploy latest version of kubeflow to my own cluster, and got stuck at the step Tring to get istio-ingressgateway Service External IP, and the error logs are:

INFO[0245] Trying to get istio-ingressgateway Service External IP  filename="existing_arrikto/existing.go:392"
Error: couldn't apply KfApp:  (kubeflow.error): Code 500 with message: coordinator Apply failed for existing_arrikto:  (kubeflow.error): Code 500 with message: timed out while waiting to get istio-ingressgateway Service ExternalIP
github.com/kubeflow/kubeflow/bootstrap/v2/pkg/kfapp/existing_arrikto.getEndpoints
	/home/jlewi/git_kubeflow/bootstrap/v2/pkg/kfapp/existing_arrikto/existing.go:288
github.com/kubeflow/kubeflow/bootstrap/v2/pkg/kfapp/existing_arrikto.(*Existing).Apply

This is my own testing kube cluster, which does not have an external IP, and it shouldn’t prevent me install kubeflow.

I tried to remove istio overlay from app.yaml, and it does not work.

kfctl version:

root@qcloud:~/workspace/kfapp# kfctl version
kfctl v0.6.0-0-g71aea0a9

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 5
Comments: 25 (9 by maintainers)

Most upvoted comments

@jlewi @halayudha sorry for the late response, and thanks, I tired latest v0.6.1-rc.2-1-g3a37cbc6 release, and also installed the metallb, and now the installation passed. However now the installation failed at some other places, and the katib-db and katib-manager pods are not running as expected, but I think I can work that out.

@JavaDerek I have exact same problem like you do, and then I found out only install metallb will not solve the problem, you’ll also need to create a config map for it, like here: https://metallb.universe.tf/configuration/. I used the basic layer2 configuration exactly like described on the doc, waited for a while, and try re-install kubeflow, and it worked.

emmayang on Jul 31, 2019