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

[frontend] Pipeline generic installation does not include a virtual service #5462

Closed
nakfour opened this issue Apr 12, 2021 · 4 comments · Fixed by kubeflow/manifests#1851
Closed

Comments

@nakfour
Copy link
Member

nakfour commented Apr 12, 2021

When installing "platform-agnostic" and trying to get to the pipeline UI from the Kubeflow central dashboard, we get "Sorry, /pipeline/ is not a valid page". Checking for virtualservices in namespace kubeflow, there are none for pipelines. Looking at the code, we dont see a VirtualService created : https://github.com/kubeflow/manifests/tree/master/apps/pipeline/upstream/base/installs/generic
While multi-user install does include a virtualservice: https://github.com/kubeflow/manifests/blob/master/apps/pipeline/upstream/base/installs/multi-user/virtual-service.yaml

@zijianjoy
Copy link
Collaborator

Thank you @nakfour for submitting this request!

@Bobgy and I have discussed about this issue and our initial thinking is to perform following refactorings:

  1. For ml-pipeline-ui VirtualService, we need to create a folder called ml-pipeline-ui under https://github.com/kubeflow/pipelines/tree/master/manifests/kustomize/base/pipeline, and put all UI related items, including virtual service file there.
  2. For metadata-grpc VirtualService, we will create a folder called virtual-service under options folder: https://github.com/kubeflow/pipelines/tree/master/manifests/kustomize/base/metadata/options. And put the virtual service definition to that folder. And put the remaining files under istio option to a new folder called multi-user option. Also we need to add a README to explain that if you want to use virtual service, you can install virtual-service option.

@zijianjoy
Copy link
Collaborator

For now, you can use the kubeflow/pipelines instead of kubeflow/manifests repo for the virtual service definition: https://github.com/kubeflow/pipelines/blob/master/manifests/kustomize/base/metadata/options/istio/virtual-service.yaml

@Bobgy
Copy link
Contributor

Bobgy commented Apr 16, 2021

@zijianjoy virtual service for ml-pipeline-ui should still be put in options folder, because it's not needed for env without istio.

@nakfour
Copy link
Member Author

nakfour commented Apr 16, 2021

@Bobgy @zijianjoy sounds good. since these VRs are common for all options to install pipelines, good idea to place them under base/pipeline

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