{"push_id":2932929823,"size":1,"distinct_size":1,"ref":"refs/heads/pr/v1.0-backport-use-separate-clusters","head":"715fdebb35813c3f4c48015362a7333d6636c70f","before":"0421a61f914de5cd15d33947373ab1d91afe73bd","commits":[{"sha":"715fdebb35813c3f4c48015362a7333d6636c70f","author":{"name":"Jarno Rajahalme","email":"0f1ab0ac7dffd9db21aa539af2fd4bb04abc3ad4@covalent.io"},"message":"envoy: Use separate clusters for egress and ingress redirects.\n\n[ upstream commit 8bd65a6bfd44b9949362999073c363273133623a ]\n\nCurrently it is possible that an ingress proxy accidentally reuses a\nconnection opened by an egress proxy, since in both cases the\nconnections share the same (original) destination address and the same\nsource security ID. Fix this by using separate clusters for ingress\nand egress redirects, as each cluster has its own connection pool.\n\nSigned-off-by: Jarno Rajahalme <jarno@covalent.io>","distinct":true,"url":"https://api.github.com/repos/cilium/cilium/commits/715fdebb35813c3f4c48015362a7333d6636c70f"}]}
{"actor":{"display_login":"jrajahalme"}}