Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CentralDashboard returns 404; Ambassador can't parse the route #1306

Closed
jlewi opened this issue Aug 3, 2018 · 2 comments
Closed

CentralDashboard returns 404; Ambassador can't parse the route #1306

jlewi opened this issue Aug 3, 2018 · 2 comments

Comments

@jlewi
Copy link
Contributor

jlewi commented Aug 3, 2018

On master Ambassador shows the following error trying to parse the route for the central dashboard

2018-08-03 06:35:54 diagd 0.30.1 ERROR: k8s-dashboard-kubeflow.yaml.1: <RichStatus BAD error=k8s-dashboard-kubeflow.yaml: could not parse YAML hostname=ambassador-7d8f87f6dc-2mbk2 resolvedname=10.20.0.10 version=0.30.1>

As a result no mapping is defined and trying to access the central dashboard behind Ambassador gives a 404.

This is ksonnet/ksonnet#670

We should be able to workaround this.

@richardsliu
Copy link
Contributor

Seems like this is fixed if the cluster is deployed using ks version 0.12+.

@jlewi
Copy link
Contributor Author

jlewi commented Aug 19, 2018

Can we still implement a work around so that we don't have to require 0.12 just to fix this?

richardsliu added a commit to richardsliu/kubeflow that referenced this issue Aug 22, 2018
k8s-ci-robot pushed a commit that referenced this issue Aug 23, 2018
saffaalvi pushed a commit to StatCan/kubeflow that referenced this issue Feb 11, 2021
yanniszark pushed a commit to arrikto/kubeflow that referenced this issue Feb 15, 2021
)

* Add check for experiment restart in controller

* Change comment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants