Kubeflow dashboard does not show in browser #1764
Comments
|
I am having similar issue now after bring up kubeflow successfully. Thanks. |
|
If I go by Kosehy suggested (clster I.P.: http://:8082/_/jupyter/), I am get an "not a valid page" error. No issue to get K8S dashboard with login token |
|
I am getting the I.P. from the following, |
|
Based on kubeflow/kubeflow#5407 (comment)
Here is what I didAfter enabling kubeflow go to "http://123.456.789.123:8081" you can login admin:1qaz2wsx However, I still cannot access pipeline and notebook servers
|
|
I grabbed the latest microk8s today and still got the same error as above. Any idea how to fix it? Thanks. |
|
@chen98 It might be certificate issue. And I also got error message inside the istio-ingressgateway log microk8s kubectl -n kubeflow get podsmicrok8s kubectl -n kubeflow logs istio-ingressgateway-6dbfc48ff-brj4g |
@chen98 I will test previous build. mutatingwebhook/validatingwebhook(m/v) issue
The connection to the server 127.0.0.1:16443 was refused issue
Empty charm patch
@chen98 I test version from 1.17 to latest. |
|
@chen98 : I installed and enabled kubeflow on a cloud virtual machine using I get a success message saying kubeflow dashboard available at http://localhost I setup SOCKS proxy on port 9999 and able to open Kubeflow page using clusterIP in the services, but unable to access pipelines and notebook server page Any idea how we can get notebook server and pipelines page working ? |
|
I am still having the same issue as you and @kosehy have, not able to access notebook server or pipeline pages. It was broken since Nov. releases. Still waiting for microk8s team response... Temporarily I switched to minikube to use kubeflow. |
|
@chen98 : Are there any older microk8s versions which work fine like 1.18/stable ? |
@chen98 Would you please share some more details about how to switch to minikube for using kubeflow? |
@danudeep90 I tested from 1.18 to latest version and only latest/edge version works. I will test 1.17 version and let you know. |
@danudeep90 Would you please share some more details about "I setup SOCKS proxy on port 9999 and able to open Kubeflow page using clusterIP in the services" part? |
|
@kosehy : Please follow the steps in the video below from 7:55 to 8:55 to setup socks proxy After that, you can get IP of the kubeflow dashboard from command below Enter the IP in your browser and you should see the kubeflow dashboard. |
@knkski : Can you help me on this issue ? |
|
@kosehy is this issue resolved for you, or still there for the new microk8s releases? |
@chen98 I will test several versions below on my local ubuntu machine now and let you know! mutatingwebhook/validatingwebhook(m/v) issue
1.19/edge: v1.19.5 2020-12-09 (1856) Inspection report |
|
Following the instructions above all pods and services come up but then webpage is empty. Ubuntu 20.04 LTS |
|
kubeflow/kubeflow#5429 (comment) microk8s and kubeflow installationAfter enabling kubeflow
kubeflow dashboard login
kubeflow dashboard UI
Now I can access pipeline. kubeflow dashboard UI
Inspection report |
|
kubeflow/kubeflow#5429 (comment) I tested two version, v1.20.0(1864) and v1.20.0(1873) Version:
microk8s status
Inspection Report: Version:
microk8s status
Inspection Report: |
|
@kosehy : Is there a fix from microk8s side so that everything works including able to access dashboard and spin up notebook servers ? If yes, Can you tell me how to install microk8s so that everything works |
|
installed: v1.20.0 (1876) 219MB classic followed the instructions above and the kubeflow page appears and i login but the page has errors:
Uncaught SyntaxError: Unexpected token '<' three times for runtime, polyfill and main.js[] Inspection report |
Actually I've been looking at the bundle making up the Kubeflow deployment and specifically the jupyter web app and the release used looks like it doesn't work. It's early in the morning and I'll try and look at this over the next couple of days but the docker image has inconsistent references to the required javascript. |
|
Finally, I found a great installation tutorial about how to install kubeflow 1.12 using microk8s. I tested 1.18/stable, 1.19/stable, and 1.20 stable version and can access kubeflow dashboard, pipeline, and notebook servers |
|
@kosehy: apologies for the slow response. Can you try running |
|
@knkski I still cannot access the notebook servers
Here is my tarball file below: |
|
I got the same issue with @kosehy installing on a fresh Ubuntu 18.0.5 |
|
Just adding to the conversation, I also tried installing I'm running on It seems the password and username set via the From what I can tell, it appears as if the JS and CSS assets aren't being served from the |
|
@kosehy, @tritran-cotai, @burningion: Sorry about the issues with this. I've got #1919 merged, which should fix these issues. Can you try it again after making sure to refresh the snap ( |
@ knkski I will try! |
|
@knkski working like a charm, both notebook servers and pipelines. Thank you very much. |
|
@knkski works great!! |
@knkski Fantastic !!! |
|
@kosehy : I tried doing a fresh installation using sudo snap remove microk8s --purge Enabling kubeflow is taking lot of time.. and still shows waited 4375s for operator pods to come up. Can you share the fresh installation instructions so that kubeflow is deployed properly @knkski: Can you help me with this ? |
|
@danudeep90: can you create a new issue with the output from |
What steps did you take and what happened:
Based on the ubuntu/microk8s#1698 suggestion,
I installed kubeflow using microk8s.
After install, I clicked the http://localhost
And I got error below
What did you expect to happen:
Enter the kubeflow dashboard.
Anything else you would like to add:
inspection-report-20201123_124046.tar.gz
When I Use the following command to set up port forwarding to the Istio gateway,
I have below error message:
When I enter the link http://10.152.183.51:8082/, I can access to kubeflow dashboard.
However, I cannot access other section, like pipelines, Notebook Servers, etc.
Environment:
kubectl version): v1.19.4-34+68a982ef7f1a98/etc/os-release): ubuntu 20.04 LTSThe text was updated successfully, but these errors were encountered: