thank you to Turbine Labs @mccv@9len@_tr @brookshelley and @lucperkins on contributing the excellent LearnEnvoy resource to the @EnvoyProxy project! https://t.co/kVzx38adJA
No matter how well you write your code, failure is always an option. See how Envoy communicates this failure back to clients, in every. single. case. https://t.co/v44e57KcXG
Find out how Nav, a financial services company, saved hundreds of engineering hours and reduced technical debt in the process by using @EnvoyProxy and @GoTurbine to migrate to Kubernetes https://t.co/5eUgYXvtqa
Learn more about how control planes work, and what makes one great in this post from the @envoyproxy blog by @brookshelley, our DevRel Engineer https://t.co/QQeszyWGqb
Local microservice development is tricky, but with Houston and @EnvoyProxy you can offload dependencies remotely and only run what you're working on https://t.co/9VGVn5S46i
With full support for custom routes, domain, and protocols from your existing config files, we think you’ll love this update to Rotor—the best @envoyproxy control plane https://t.co/vlaXXbjSnb
Introducing #EnvoyCon, the first dedicated @EnvoyProxy conference (just before #KubeCon + #CloudNativeCon Seattle) 🎉🌟 and the CFP is now OPEN – get your talks submitted by Aug. 24‼️ https://t.co/C4s1CevBIe
Connecting Rotor to Houston gives you a full-featured, collaborative traffic management solution, built on @envoyproxy—find out how: https://t.co/v8lpQ2P9u3
Check out this run-through of Rotor, a lightweight xDS server with service discovery for @EnvoyProxy. @brookshelley walks us through @HashiCorp's Consul services being collected by Rotor, and routed by Envoy. There might even be some farm animals.