powerful-knife-41200
10/28/2024, 11:43 AMhundreds-zebra-57629
10/28/2024, 8:58 PMMETAFLOW_S3_ENDPOINT_URL
in step 10.
3. If you are trying to get the metaflow UI working as well, there is a bit of an unsolved challenge (afaik). The UI backend pod uses the same METAFLOW_S3_ENDPOINT_URL
specified on your local mf config. Which means the DNS/IP you use there needs to be accessible both from your local machine and the UI backend pod. This is not an issue if your local setup is in the same network perimeter as the UI backend pod. However, if it is not, you will need to figure out how to make the same name resolve to the same IP both locally and from the UI backend pod. One hacky solution is to set the minio k8s service domain as the ``METAFLOW_S3_ENDPOINT_URL` this means UI backend can easily resolve the domain. For the local part, you can port-forward the minio pod and then edit /etc/host
to point the minio k8s service name to the localhost domain. This will make the service name resolve to localhost on your machine. Of course there maybe better solution out there. (I'd encourage you to share if you come up with a better approach).
Finally, I haven't tried running argo-workflows on-prem, but I don't believe there would be any gotchas there.
Also, please do share in this thread the issues you deem relevant in this thread and we can attempt to address them.adorable-oxygen-86530
10/29/2024, 7:08 AMpowerful-knife-41200
10/29/2024, 8:35 AMpowerful-knife-41200
10/29/2024, 8:37 AMadorable-oxygen-86530
10/29/2024, 8:39 AMpowerful-knife-41200
10/29/2024, 9:03 AMpowerful-knife-41200
10/29/2024, 9:04 AMbumpy-piano-21462
11/11/2024, 6:57 PMadorable-oxygen-86530
11/11/2024, 7:05 PMadorable-oxygen-86530
11/11/2024, 7:06 PMbumpy-piano-21462
11/11/2024, 8:04 PMadorable-oxygen-86530
11/11/2024, 8:13 PMbumpy-piano-21462
11/11/2024, 9:20 PM