Kevin Shelaga

This change should include the ability to view RTs in the UI.

thank you @DuncanDoyle As i mentioned in my submission the customer wants to have a generic set of exposeHeaders at the VS level which platform engineers will enforce across all...

@nfuden Gloo pod name, though potentially this could include pointing Glooctl to different proxy names as well

@supalp a new ticket was created as a a milestone of sorts https://github.com/solo-io/gloo/issues/9274

reopening for backport to 1.13

I have communicated that this is an issue with the underlying frameworks to the customers and unfortunately there is nothing envoy can do to fix the issue. The prescribed workaround...

Initial investigation looks like there is excess go routines causing the errors, but why this happens more on a clean install with EKS and not AKS/GKE, i do not know....

bumping your ulimit usually fixes this

I believe the issue is using a private cluster, not the shared VPC. Using a private cluster with your own VPC or the default still results in the same failed...

@tomekzielins im still seeing issues after adding 7888, do you have other ports added which might of helped?