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

Connect local notebook to remote Pipeline cluster #1079

Closed
IronPan opened this issue Apr 4, 2019 · 2 comments
Closed

Connect local notebook to remote Pipeline cluster #1079

IronPan opened this issue Apr 4, 2019 · 2 comments
Assignees

Comments

@IronPan
Copy link
Member

IronPan commented Apr 4, 2019

Currently if a Jupyter notebook runs locally, the DSL doesn't know the host name of the pipeline cluster. It assumes the pipeline is accessible through a port-forwarded local port, and it uses localhost:8080/pipeline/* to connect to the Pipeline server.

This doesn't work in case of the cluster is accessible only through IAP or basic auth.

Instead, the notebook should direct the traffic to the right hostname, following by the steps below

  1. Run kubectl -n kubeflow port-forward service/ml-pipeline 8888:8888
    (as opposed to kubectl port-forward svc/ambassador -n ${NAMESPACE} 8080:80)
  2. Modify Client() if you aren't running in cluster run the following kubectl command to get the ingress end point
    • e.g. shell out to
      kubectl -n kubeflow get ingress -o jsonpath='{.items[0].spec.rules[0].host}')

The ingress endpoint will look like https://kf-vmaster-n01.endpoints.kubeflow-ci-deployment.cloud.goog/pipeline/#/runs/details/247f400d-5660-11e9-81a3-42010a8e00c8

@kevinbache
Copy link
Contributor

related: #780, #590

@vicaire
Copy link
Contributor

vicaire commented Apr 11, 2019

Resolving in favor of #780 (support to run notebooks locally)

@vicaire vicaire closed this as completed Apr 11, 2019
magdalenakuhn17 pushed a commit to magdalenakuhn17/pipelines that referenced this issue Oct 22, 2023
* Validation check for InferenceService Name

. Check if ISVC name starts with alphabetical character.

Fixes kubeflow#1059

* Change the point of ASCII code to check if alphabet or not

* Validate ISVC name with Regexp

* . Add unit tests
. Move const and var section on the top

* Apply regular expressions for validation of isvc name to v1beta1

* Remove validation for Max length of isvc name, because default and
canary have different length.
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

5 participants