Envoy Series: Envoy xDS Dynamic Configuration and Control Plane Interactions - Part 4

[@vivekmishra69]

Really awesome series. Presented really well and very easy to understand. Would love to see a series on control plane.

[@soloio_inc]

Thank you! What topics in the control plane series would you like to see covered? if too long for youtube comment, open an issue here with the details: github.com/solo-io/hoot/issues

[@vivekmishra69]

@@soloio_inc Design consideration for a control plane implementation. Why there are so many control plane implementations? Scalability and observability of control plane components itself may be using Istio as an example. Performance, security and best practices. Extending the existing control plane solutions. Integration with different types other dataplane solutions apart from Envoy. These are some of the topics I can think of as I don't have much idea of control plane.

[@ellouzefarouk6741]

Very good video. It should put in the Envoy website as a useful resources. Thank you for the effort men

[@alexandera1688]

Thank you, It was helpful.

[@kamesh7818]

very useful talk. thank you

[@brendandoyle3947]

Hi nice videos I have a couple of questions... 1) Can you have the control plane talk to more than one instance of envoy? I suspect yes and they are idetified by the "id" in the yaml (referenec video at 39.46 min) . How is this ID defined is it just something agreed between envoy and the controler plane? 2) Can this be configured to be a push model rather than pull control plane pushes update s to envoy instances? and if so how? 3) Are there any reference implmentations of a control plane, preferably in python using REST API not grpc?.

[@YuvalKohavi]

yes, that's right. the controlplane gets the client identity and servers configuration based on that. how it does it is up to the control plane.. 2) yes, the grpc go control plane (the one used in the video) is a push model. envoy connects to the control plane, and the control plane publishes configuration updates. 3) see here for go and java reference impl: github.com/envoyproxy; they are grpc, not REST unfortunately. if you want to have push semantics, then you have to use gRPC