Dashboard command does not return and work

[nvashish123]

in the 201-cluster-monitoring part -

when the command is run to create the Dashboard, the dashboard url is not accessible by either the full URL - http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/

or by just accessing the localhost - 127.0.0.1:8001

I am not on amazon VPN while trying this.

[christopherhein]

To confirm this was while using kubectl proxy ?

[nvashish123]

correct, using kubectl proxy

[riywo]

Since the proxy is running on the Cloud9 instance, you can hit the localhost:8001 from Cloud9 shell by curl. But accessing from your local browser is not available to localhost:8001.

Cloud9 has a functionality called "preview", which is a Cloud9 provided proxy to port 8080 on Cloud9 instance, so I'd tried to access https://aaaaaaaaaaaaaaaaaa.vfs.cloud9.us-east-1.amazonaws.com/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/ , but it returns 403.

[diegodalmolin]

Solved this by:
1 - installing kubectl locally at my workstation
2 - exporting cloud9 .kube/config file (kubectl config view --flatten=true)
3 - Imported that to my workstation .kube/config
4 - run kubeclt proxy locally.
5 - open 127.0.0.1:8001

thanks Omar

[arun-gupta]

@nathanpeck experienced this in a recent workshop as well. Similar to #377

[christopherhein]

We probably should put this on hold until - kubernetes/kubernetes#46517 since then in Cloud9 we could have it bind to 0.0.0.0 and the preview "should" (famous last words) should work. 👍

[subhrang]

Thanks diegodalmolin.
Your method worked

[ghost]

Per issue comment here and here suggested following two work on Cloud9 ide preview:

kubectl proxy --address 0.0.0.0 --accept-hosts '.*' --port 8080
kubectl proxy --address 0.0.0.0 --disable-filter=true --port 8080

URL should change to as previous @riywo mentioned above from localhost to Cloud9 preview address.

Just for the record, in case you "really" need to run kubectl proxy on Cloud9 ide preview.

[christopherhein]

thanks @minghsieh-prenetics ! Did you test this? If so would you be interested in putting in a Pull Request with the documentation changes?

[ghost]

@christopherhein Yes I did. We, however, will need to map other ports (e.g. 401-configmaps redis port, and other 4xx level sections, etc.), depends on context / workshop section materials. PR certainly will put at that time.

[ghost]

@christopherhein 👆 PR.

[ghost]

@nvashish123 Could you test it please? If it's ok for you then please close this issue.

[riywo]

It worked for me! Excellent!