Hacker News new | past | comments | ask | show | jobs | submit login

So many service meshes these days, how would this differ from Istio which seems to be the hot topic alongside Kubernetes?



Unlike Istio, this is built to work natively with minimal dependencies on every platform, not exclusively on Kubernetes, which means it can support both new greenfield applications and existing VM-based apps, so that networking policies that would typically be available only on K8s for new apps, can be applied on existing workload today. That, and it’s meant to be easier to use, which is another big problem with existing Service Mesh implementations.


Can you use Kuma and Istio together if you already have Istio in one environment?


Interesting point, would love to know as well. And I echo meddlepal’s sentiment since there are so many options it can feel overwhelming. But for someone who still have services on bare metal, would folks agree that this is a good product to explore?




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: