3 ms·
Interesting. Curious to hear why they went with Kuma/Envoy and not Istio or Consul
by _adrien_ 5y ago
Interesting. Curious to hear why they went with Kuma/Envoy and not Istio or Consul
- fosk 5y agoKuma's architecture has been built in such a way that the multi-zone support is native in the product and not an afterthought. This is significant, since policy storage, policy propagation, policy reconciliation, error handling and so on is natively built inside the core architecture, with 1st class support for Envoy since day one. It abstracts Envoy concepts into "policies" that are easier to apply and use, it provides a more stable API and experience across distributed workloads, and it also includes native support for VM applications. Even Kelsey Hightower loves it [1]. [1] https://twitter.com/kelseyhightower/status/1280539821564243970?lang=en https://twitter.com/kelseyhightower/status/12805398215642439...