{"id":88734,"date":"2019-02-22T13:00:32","date_gmt":"2019-02-22T11:00:32","guid":{"rendered":"https:\/\/www.javacodegeeks.com\/?p=88734"},"modified":"2019-02-21T09:52:14","modified_gmt":"2019-02-21T07:52:14","slug":"control-plane-envoy-pluggability","status":"publish","type":"post","link":"https:\/\/www.javacodegeeks.com\/2019\/02\/control-plane-envoy-pluggability.html","title":{"rendered":"Guidance for Building a Control Plane for Envoy – Build for Pluggability"},"content":{"rendered":"

Envoy is a very powerful piece of software and every day new use cases and new contributions are being proposed to the community<\/a>. Although the core of Envoy is very stable, it\u2019s built on a pluggable filter architecture<\/a> so folks can write new codecs for different L7 protocols or add new functionality. At the moment, Envoy filter\u2019s are written in C++ and there is an option to extend Envoy with Lua<\/a> but there is also some discussion to support Web Assembly<\/a> for extensibility as well. Alongside the fast-moving Envoy community and the need to configure these new capabilities, there is also the need to include new domain-specific object models to support new platforms that want to take advantage of Envoy. In this section, we\u2019ll explore extending an Envoy control plane along both of those dimensions.<\/p>\n

Extending Envoy is fairly straight forward by writing C++ filters. Envoy filters we\u2019ve created on the Gloo project<\/a> include:<\/p>\n