Hello, we have deployed Metaflow on GKE using Argo, but are having trouble with the Metaflow UI accessing the Metaflow Service (getting a 404 response). Hitting

api.<our-service-dns>/ping

returns

pong

(mentioned here) so it seems as though we are able to at least access the service. We are also able to run jobs, which we can track through Argo. Any idea what might be going on here? cc: @ripe-car-38698

Thank you Patrick! The

/api/docs

is indeed returning a 404, and also everything

/api/*

in general

In the UI service, did you set the env var

PATH_PREFIX

to

/api

? It’s been a while since I set this up so not sure, but I think I recall running into something like this It depends on your exact setup but may be relevant for y’all. I found where this is mentioned here: https://github.com/Netflix/metaflow-service/blob/master/services/ui_backend_service/ui_server.py#L27

Hello @gray-window-97284! Thank you for the reply! We are not touching the configuration of Metaflow at that level in our chart, and indeed in the metaflow template its already set by default:

- name: PATH_PREFIX
  value: "/api"