When will a

public.ecr.aws/outerbounds/metaflow_ui:v2.2.4

equivalent https://gallery.ecr.aws/outerbounds/metaflow_ui_backend be built? thanks!

so we had a bit of a back and forth with how to split metadata service, backend and UI into container images (make 3 images? make one uber-image? make one image for backends and one for front-end?)

I see images for: • UI front-end: https://gallery.ecr.aws/outerbounds/metaflow_ui • Metadata service: https://gallery.ecr.aws/outerbounds/metaflow_metadata_service • But not for the

metaflow_ui_backend

here https://gallery.ecr.aws/outerbounds/metaflow_ui_backend

right that's because the UI backend is included in the second image

ah I see https://github.com/Netflix/metaflow-service/blob/3bd9b4683fe4028d0fa92a391b31b4a5a742d62c/Dockerfile#L31

but the configuration we use internally, and CFN/terraform/helm templates, and regularly build images for is: 1. an image with UI react app 2. an image with Metadata Service + UI Backend

do you have links to helm? So I can see how I can run #2 from the image thankyou

sweet!: health/livenessProbe could use https://github.com/Netflix/metaflow-service/blob/87723ac4ef8ab44a7bfb7fb9a3af4b1e9c14e630/services/metadata_service/api/admin.py#L59-L60

that's up to you really, in k8s we run an ingress in front of it and route

/api

and

/static

to different deployments