We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
The text was updated successfully, but these errors were encountered:
Seems like this is fixed if the cluster is deployed using ks version 0.12+.
Sorry, something went wrong.
Can we still implement a work around so that we don't have to require 0.12 just to fix this?
Fix kubeflow#1306
28adf6c
Fix annotations in ambassador and centraldashboard (#1399)
fce0f86
* Fix #1306 * Format jsonnet * Comments
Fix annotations in ambassador and centraldashboard (kubeflow#1399)
b8a36d5
* Fix kubeflow#1306 * Format jsonnet * Comments
Fix restart check in controller for completed experiments (kubeflow#1306
ced8496
) * Add check for experiment restart in controller * Change comment
No branches or pull requests
On master Ambassador shows the following error trying to parse the route for the central dashboard
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.
The text was updated successfully, but these errors were encountered: