I’m trying to run temporal on kubernetes and when I run a workflow it times out. I’ve tracked it down to the frontend giving me this error: unknown service server.matchingservice.v1.MatchingService . I’m thinking there’s probably a network configuration problem, but I wanted to see has anyone else seen this? Any ideas how I can troubleshoot this?
2 Likes
Hey Kyle, thank you for playing with Temporal!
I haven’t seen this problem – we do run test workflows in our test pipelines against instances of temporal running in Kubernetes, deployed with Temporal helm charts.
I am curious, how did you deploy temporal, did you happen to use temporal helm charts, or did you do something else?
Thank you!
Mark.
Just following up on this, I’m not sure what the problem was, but I pulled the latest helm chart last week and used the latest release (0.27.0) and that seems to have fixed the problem :-).
3 Likes