You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Run kubectl -n kubeflow port-forward service/ml-pipeline 8888:8888
(as opposed to kubectl port-forward svc/ambassador -n ${NAMESPACE} 8080:80)
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}')
* Validation check for InferenceService Name
. Check if ISVC name starts with alphabetical character.
Fixeskubeflow#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.
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
(as opposed to kubectl port-forward svc/ambassador -n ${NAMESPACE} 8080:80)
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
The text was updated successfully, but these errors were encountered: