Alec Holmes

Woah okay super weird behavior the integration test doesn't even pass on your branch. Getting very different outputs than on my branch, this is great thanks for doing this. I'll...

I guess this brings me to my next question, do we want to hold off on the server ordering PR before we guarantee cache order? I'll still try and figure...

Okay quick update, @sunjayBhatia on your branch if I turned off the cache logging I see the same output on the upstream branch. So LDS and CDS still come first...

> hm, i've increased the number of snapshots generated but I've never seen the tests actually fully fail or that crash, guess I'll have to run it a few more...

@maplebeats and @sunjayBhatia Can you guys test again? I just pushed this commit: https://github.com/envoyproxy/go-control-plane/pull/544/commits/1016a43c39ae71be92a7f9dc60de59e9742f8241 I was able to see that the cache logs lined up with the server logs in...

I'd like to actually revisit this but potentially widen the scope? Would people be interested in other "builders" as well such as circuit breaking policies, outlier detection, rbac, etc..? Anything...

For this API I imagine something like this: ## Builder ```go // Builder defines a global API for various policy engines // that are targeted towards various service mesh core...

That's definitely true, the Envoy API is expansive and difficult to keep up with. You are right in thinking that if we went this route we'd take on the responsibility...

Ah we need to remove the stale label here

Right so xds-relay wasn't a control plane. It was more of a shim/translation layer if I understood that project correctly. I imagine we can set standards in this project for...