https://dagster.io/ logo
#ask-community
Title
# ask-community
a

Andriy Mykhaylyk

05/11/2023, 8:33 AM
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?
🤖 1
a

Adam Bloom

05/11/2023, 11:40 AM
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?
a

Andriy Mykhaylyk

05/11/2023, 11:41 AM
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.
a

Adam Bloom

05/11/2023, 11:53 AM
Ah - it might just need the same update then? Feel free to link to this one in a PR
a

Andriy Mykhaylyk

05/11/2023, 12:11 PM
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.
a

Adam Bloom

05/11/2023, 12:32 PM
Hopefully someone from the dagster team knows!
d

daniel

05/11/2023, 2:32 PM
Sent out a fix to merge this in to the cloud agent helm chart as well
a

Andriy Mykhaylyk

05/11/2023, 8:17 PM
thank you for quick resolution! 🙇
4 Views