Pipeline UI should work behind Kubeflow reverse proxy (Ambassador)

[jlewi]

Opening this issue to track getting the pipelines UI to work with the Kubeflow proxy.

@yebrahim @IronPan @kunmingg Does anyone know the current status of this?

IIRC based on our discussions, I think the UI works with Kubeflow reverse proxy with the exception of the TensorBoard links. The short term fix for the tensorboard links was to explicitly map "/data" and maybe some other paths used by TensorBoard to the pipelines UI.

Do we already have issues tracking that?

[yebrahim]

As you said, the UI works fully behind Ambassador, including proxying Tensorboard with the /data route mapped to go to the Pipelines frontend service.

@neuromage is looking into better support for Tensorboard, possibly by using a CRD to manage instances.

[jlewi]

@neuromage Do we have issues tracking the tensorboard problems?

[neuromage]

There's an existing internal bug for tracking this, I'll cc you on that one. Also, I'll create a new github issue to track this externally as well.

[neuromage]

Created tracking issue #443

[yebrahim]

Closing this since it's not tracking anything now.