Teju Nareddy
Teju Nareddy
ESPv2 supports tracing, but AFAIK Cloud API Gateway did not enable it for their managed deployments of ESPv2 unfortunately. There are some concerns with trace sample rate and propagating the...
Can we re-open this? We also see similar issues. This results in the request error with HTTP 503, which our retry policy then retries.
@qiwzhang could you take a look?
Hi @qiwzhang , assigned this to you. I saw you already started researching it
> and I don't know how stock envoy can be killed, but not ours. https://github.com/envoyproxy/envoy/blob/3752119b94ae4a5ff337364f585f54305406dc7f/source/server/server.cc#L849-L873 Maybe `SIGINT` instead of `SIGTERM`?
Hi @lvl99 , what flags are you passing to ESPv2 on Cloud Run? ESPv2 should auto-detect the service account you specified in `gcloud run deploy` and use it to publish...
One more question: Is the service account above from the same project that you deploy ESPv2 to? Or is the service account from a different project?
Thanks for the info. That is very odd, as far as I can tell, everything is set up correctly. This is the first time I've seen permission issues for Cloud...
@qiwzhang I think we forgot to expose the flag?
I recommend you go ahead and duplicate the config to include `/customer/customers/update` - it's an easy fix on your end and does not require any change in your clients.