looks like the same info that’s in https://github.com/allegroai/clearml-helm-charts
which is what i’ve been working off of. persistent volumes are completely gone.
was it ever discovered if this was pushed to the latest cloud helm chart?
which i was just looking at something like that before you responded, so i was going down the right path.
seems to only happen when going through the app
istio routes based off of hostname so the app hostname was being passed causing the loop
no… they function as nfs mounts and are configured as such in the current deployment.
yeah all the hosts have the same nfs mounts. it’s what we use to store any kind of state that we need to for apps/services to allow it to run on any host without having to duplicate data.
storage classes and provisioners don’t really work because we aren’t trying to create anything new, which is why we use persistent volumes vs storage classes.
we got it running. waiting for my coworker to give me the summary of what he did... he said it was something in the nginx config though
so it seems to be how istio is handling the routing. if we use the internal service address in the nginx configs it seems to go ok.
istio expects a certain host and whatever is getting passed by the pod isn't right.
right… it’s nginx that needs to be set. glad to hear it’s going to be updated though.