Kuma, a new universal service mesh
1–10 of 36 posts
Re: Kuma, a new universal service mesh
#2Semi-tangential: I found it really interesting that Kong linked to HN/newest in the announcement email they sent out instead of directly to the HN conversation. Clever way to avoid getting their votes penalized, maybe?
Re: Kuma, a new universal service mesh
#3So many service meshes these days, how would this differ from Istio which seems to be the hot topic alongside Kubernetes?
Re: Kuma, a new universal service mesh
#4Finally a service mesh that runs natively on K8s and VMs.
I wonder what dependencies they require for VM-based installations?
Re: Kuma, a new universal service mesh
#5anyone else randomly got added to their mailing list?
Re: Kuma, a new universal service mesh
#6Yet Another Service Mesh.
Re: Kuma, a new universal service mesh
#7anyone else randomly got added to their mailing list?
Yep
Re: Kuma, a new universal service mesh
#8So 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.
Re: Kuma, a new universal service mesh
#9So many service meshes these days, how would this differ from Istio which seems to be the hot topic alongside Kubernetes?
[deleted]
Re: Kuma, a new universal service mesh
#10anyone else randomly got added to their mailing list?
Yes.