Hi! I'm not 100% I'm hitting a prodigy bug or a kubernetes bug, so apologies if this is not the right forum. I'm hosting prodigy on my k8s clustering with an ingress config like
This is definitely testing my Kubernetes knowledge , but my initial instinct is to make sure that you're pointing to the right port as well. Also, just to check, what command are you running inside of your Prodigy container?
(replace my_dataset etc by the actual name). The ports are pointing through the right thing, since when I change the path to / it works. So not quite sure.