Aniruddha Maru

Not sure why `validators.validate()` isn't called in `reload` - I added some default values using validation which seem to get blown away on `reload`.

Almost looks like `x-google-backend` is not being respected?

Update: seems like this was caused by IPv6. Adding `--backend_dns_lookup_family=v4only` to ESPv2_ARGS fixes the problem but I don't know if that's expected usage.

No, I'm deploying ESPv2 in App Engine Flex. I don't know why `.appspot.com` urls fail to resolve with ipv6 either..

Well, I just deployed ESP docker container to app engine flex using custom runtime (didn't use `endpoints_api_service` since that doesn't support v2 as you mention). It.. almost works? #171 is...

That error is from the IAP connection _downstream_ from ESP actually. The IAP in front of ESP works just fine and ESP doesn't prefer [IAP header](https://github.com/GoogleCloudPlatform/esp-v2/blob/04043537eaeab12dd2e053cd392dda7974c6f1ba/src/go/configgenerator/listener_generator.go#L331). The problem is in...

@nareddyt I got that from ESPv2 logs. Confirmed it with a hello world app that dumps headers as well. @qiwzhang I had to add audience query param, but yes, this...

Per [IAP docs](https://cloud.google.com/iap/docs/authentication-howto#authenticating_from_a_service_account) looks like there's a different way to get the token needed for authenticating against IAP?

Update: Adding `?format=full` to the metadata endpoint works and returns this: ``` { "aud": "", "azp": "103551354333791234484", "email": "@appspot.gserviceaccount.com", "email_verified": true, "exp": 1591039587, "google": { "compute_engine": {...} }, "iat": 1591035987,...

> ESPv2 will be running in the same container as backend application, but in two different processes. Yep that's what I ended up doing. Except instead of putting application code...