Accessing Kubeflow UIs

    Kubeflow includes a number of web user interfaces (UIs). This document providesinstructions on how to connect to them.

    The Kubeflow UIs include the following:

    • A central Kubeflow UI for navigation between the Kubeflow applications.
    • Notebook Servers for Jupyter notebooks.
    • Katib for hyperparameter tuning.
    • Artifact Store for tracking of artifact metadata.

    Instructions below indicate how to connect to the Kubeflow central UI. Fromthere you can navigate to the different services using the left hand navigationbar.

    The central UI dashboard looks like this:

    How you access the Istio gateway varies depending on how you’ve configured it.

    If you followed the guide to deploying Kubeflow on GCP,the Kubeflow central UI is accessible at a URL of the following pattern:

    The URL brings up the dashboard illustrated above.

    If you deploy Kubeflow with Cloud Identity-Aware Proxy (IAP), Kubeflow uses the service to provide an SSL certificatefor the Kubeflow UI. For troubleshooting issues with your certificate, see theguide tomonitoring your Cloud IAP setup.

    If you didn’t configure Kubeflow to integrate with an identity provider and performany authorization then you can port-forward directly to the Istio gateway.

    • You’ve deployed Kubeflow on GCP using the or the default settingswith the CLI deployment. (If you want touse port forwarding, you must deploy Kubeflow on an existing Kubernetescluster using the .)

    • You’ve configured the Istio ingress to only acceptHTTPS traffic on a specific domain or IP address.

    • You’ve configured the Istio ingress to perform an authorization check(for example, using Cloud IAP or Dex).

    You can access Kubeflow via kubectl and port-forwarding as follows:

    • Use the following command to set up port forwarding to the.
    • Access the central navigation dashboard at:
    • Depending on how you’ve configured Kubeflow, not all UIs work behindport-forwarding to the reverse proxy.

    For example, if you deployed Kubeflow with an ingress serving athttps://example.mydomain.com and configured an applicationto be served at the URL , then theapp may not work when served on because the paths do not match.