Getting 500 from an service behind Pomerium

Usual OAuth flow
xyzpomerium --version or /ping endpoint):pomerium/v0.7.0 (+github.com/pomerium/pomerium; d780281; go1.14.1)
Using Google IDP
```config.yaml
## What did you see in the logs?
```json
{
"level": "info",
"X-Forwarded-For": [
"1.1.1.1"
],
"X-Forwarded-Host": [
"auth-domain"
],
"X-Forwarded-Port": [
"443"
],
"X-Forwarded-Proto": [
"https"
],
"X-Real-Ip": [
"1.1.1.1"
],
"ip": "10.3.68.142",
"user_agent": "Go-http-client/1.1",
"referer": "https://domain/",
"req_id": "caa5b7b2-a2fb-ea41-6110-0af3384a16ce",
"error": "internal/sessions: session is not found",
"time": "2020-04-06T16:50:36Z",
"message": "authenticate: session load error"
}
Add any other context about the problem here.
Thanks @shreyu86 , will need to dig a bit deeper to see if this is helm chart related (no breaking changes jump to the top of my head) or kubernetes specific.
In my limited testing on K8s and docker-composed based environments, I haven't hit this though I haven't tried with the latest helm chart + updating the image. Though there's not much logging, it _looks_ this stems from some sort of connectivity issue when a gRPC client is timing out trying to contact another serivce.
\cc @travisgroth
Related
@shreyu86 I believe this was due to a regression in our pinned version of gRPC and should be fixed with #609 and be on latest. Would you be able to confirm?
Thanks!
@desimone thanks! I'll checkout this week.
@desimone confirmed this is working correctly. Currently on
pomerium/0.7.5 (+https://wwww.pomerium.io; 3149e54; go1.14.2)