Kuma, a new universal service mesh • Hacker News Board

Re: Kuma, a new universal service mesh

#21

Post by romaaeterna » Tue, Sep 10, 2019, 5:25 PM UTC

gagabity wrote: post #14

Kuma means vagina in Swahili, vagina.io is kinda funny.

In Greek, it's a "pregnant thing" or "swollen thing". Homer uses it to describe waves.

Re: Kuma, a new universal service mesh

#22

Post by bogomipz » Tue, Sep 10, 2019, 5:32 PM UTC

The documentation states:

>"It can be used natively in Kubernetes via CRDs or via a RESTful API across other environments, and it doesn't require a change to your application's code in order to be used."

Sorry if this is naive question but I'm not that up on service meshes. Aren't other service meshes generally implemented as sidecar containers? Why wouldn't those also be considered native? Could someone help me understand the distinction of a native service mesh vs non-native? I'm having a hard time getting my head around it.

Re: Kuma, a new universal service mesh

#23

Post by cfors » Tue, Sep 10, 2019, 5:43 PM UTC

This is the way forward for service meshes. Consul connect is doing something very similar.

The early service meshes were all built on top of Kubernetes, due to the fact that k8s/etcd is an easy platform to build control planes on top of (SD, networking, etc. already done) but very few large companies are ready to move everything over to Kubernetes.

Re: Kuma, a new universal service mesh

#24

Post by _nhynes » Tue, Sep 10, 2019, 5:51 PM UTC

meddlepal wrote: post #6

Yet Another Service Mesh.

Yet Another YASM. YAY!

Re: Kuma, a new universal service mesh

#25

Post by [deleted] » Tue, Sep 10, 2019, 6:00 PM UTC

adrianpike wrote: post #2

Semi-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?

[deleted]

Re: Kuma, a new universal service mesh

#26

Post by tomjohnson3 » Tue, Sep 10, 2019, 6:41 PM UTC

moimikey wrote: post #5

anyone else randomly got added to their mailing list?

Yes. ...that was very annoying.

How did they do that, exactly?

Re: Kuma, a new universal service mesh

#27

Post by benologist » Tue, Sep 10, 2019, 7:45 PM UTC

tomjohnson3 wrote: post #26

moimikey wrote: post #5

anyone else randomly got added to their mailing list?

Yes. ...that was very annoying. How did they do that, exactly?

Scraping and storing email addresses is how it usually happens, but most companies recognize it as illegal.

Re: Kuma, a new universal service mesh

#28

Post by [deleted] » Tue, Sep 10, 2019, 8:04 PM UTC

heurist wrote: post #15

Y'all emailed me without me giving you my email address. Please don't do that

[deleted]

Re: Kuma, a new universal service mesh

#29

Post by rucciva » Wed, Sep 11, 2019, 6:56 AM UTC

bogomipz wrote: post #22

The documentation states: >"It can be used natively in Kubernetes via CRDs or via a RESTful API across other environments, and it doesn't require a change to your application's code in order to be used." Sorry if this is naive question but I'm not that up on service meshes. Aren't other service meshes generally implemented as sidecar containers? Why wouldn't those also be considered native? Could someone help me unde…

The other service mesh are indeed native in Kubernetes. What Kuma emphasize as being different with others is the "via a RESTful API across other environments", so it support both orchestrated container environment and legacy environment.

Re: Kuma, a new universal service mesh

#30

Post by rucciva » Wed, Sep 11, 2019, 6:56 AM UTC

Cool news! Just wondering about something. "API Management is Dead", said Kong's CEO in Kong Summit 2018. And then, first Kong GA ship with service mesh capabilities, making it capable for both north-south and east-west (API) traffic management. But now that they released Kuma with Envoy as the data plane, will that means Kong will be focused on being the API Management that they proclaim as being dead? Will the service mesh capability on Kong be removed?