greetings. we've encountered the same problem as described here with Istio - because services created by cloud-agent use the wrong port name (

http

instead of

grpc

) cloud-agent times out for grpc healthchecks. do you know if there's any way around to fix it? to specify service port name in dagster-cloud?

Hey, we’re not running dagster-cloud, but we’re running dagster with istio. One of my team mates updated that value in the chart last year (see the version on `master`: https://github.com/dagster-io/dagster/blob/master/helm/dagster/charts/dagster-user-deployments/templates/service-user.yaml). Are you using an extremely old helm chart version?

thanks for the answer! the issue is that we're using

dagster-cloud-agent

chart and not the

dagster-user-deployments

chart, and I see no way how we can configure it for our case.

Ah - it might just need the same update then? Feel free to link to this one in a PR

the thing is I'm not sure where to open a PR - i don't see a clear reference on how/where cloud-agent creates/defines these services.

Hopefully someone from the dagster team knows!

Sent out a fix to merge this in to the cloud agent helm chart as well

thank you for quick resolution! 🙇