[cube2222]

Hey, I myself am planning to introduce envoy into an existing mixed kubernetes/bare-metal architecture, having the same "one service at a time" considerations.

Have you been thinking about adopting istio? If yes, why didn't you?

[ckwang]

We're currently evaluating the pieces that comprise Istio, both within Kubernetes and outside of it in our existing infrastructure.

We didn't do so immediately because we did not want to immediately update all of our technology at once and felt that a piece-wise migration would be both the least disruptive to our infrastructure and safest. I think of Istio as like Smartstack in that it's not actually a complete "thing" so much as a suite of technologies that can be individually evaluated and deployed. It's very easy to fall into the trap of wanting to do everything at once, and we opted to make small progressive steps for this initiative.

[cube2222]

Yeah, I'm thinking of going with only the minimal istio installation (pilot only), not to roll our own, and setting it up with our existing consul service Discovery.

[ckwang]

That's pretty close to our next immediate steps as well :)