I’ve been looking for a good comparison to using the integrated Kong Service mesh for east-west micro-service interaction control vs. integrating with Istio. The available Kong mesh documentation is very light compared to Istio, and it seems there is not a lot of user feedback on the web yet.
- Does Kong allow for dynamic routing based on content (e.g. http header attributes like user) as Istio does?
- What are the main differences between Kong mesh and Istio integration?