eddy-curv

@DazWilkin same issue here

This also happens to me on GKE v1.18.17-gke.1901 and the following terraform versions: Terraform v0.13.7 + provider registry.terraform.io/hashicorp/kubernetes v1.13.2 regardless of the initial value of `allow_volume_expansion`, changing it in terraform...

I also [asked](https://datawire-oss.slack.com/archives/CAULN7S76/p1613058763440600) in the Ambassador slack channel, and Noah Krause answered me: > Hey eddy, sorry for the late response. Recent versions of Ambassador have released with an update...

@kflynn, For about a year now we used Ambassador OSS with configuration from file system. This served us well for having a single source of truth for our local dev...

Despite using version 1.5.0 of Ambassador OSS and adding `preserve_external_request_id` to ambassador.yaml, x-request-id is still overridden by Ambassador. I inspected the aconf.json and ir.json and found out that ir.json lacks...

Additionally, if I use preserve_external_request_id but have TracingService enabled, which once gets precedence? will x-request-id be overwritten regardless?

Thanks @prakharjoshi, can you also address my question about TracingService? If preserve_external_request_id is true but I also have TracingService enabled, will the value of `x-reqeust-id` be overridden by TracingService? I'm...

Thanks @prakharjoshi, really hope that the IR module flow will be fixed, we would really like to use that preserve_external_request_id ability.

@prakharjoshi The functionality works as expected, many thanks!

After closer inspection, it seems like the 14th character of `x-reqeust-id` value will be overwritten due to [envoy's behaviour](https://github.com/envoyproxy/envoy/issues/11532). for example, `aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee` will be modified to `aaaaaaaa-bbbb-9ccc-dddd-eeeeeeeeeeee`. Can something be...