11–20 of 23 posts
This looks like an interesting off the shelf alternative to Envoy, which currently requires you to implement your own control plane. Moving forward, is this going to be open-core with a paid EE edition type of thing like Traefik?
Using Traefik for more than a year now, working like a charm.
I wonder if SO_KEEPALIVE is implemented ? I ask this because we have funny devs that don't know how to implement SO_KEEPALIVE on springboot projects correctly. That can be annoying for an Operation Team....
Is Maesh a newer imagining of what Linkerd v1 sought to do? Is it a better k8s-integrated solution?
What is up with these names? For a moment I felt either dyslexic or like I’m experiencing a stroke.
https://www.consul.io/docs/connect/index.html
I wish more open-source products would write semi-neutral explanations of what their project is, isn't and how it compares to some similar services.
For example, I think Kubernetes does a pretty good job of explaining what it isn't.
https://kubernetes.io/docs/concepts/overview/what-is-kuberne...
I'd love to see a comparison between Maesh and Linkerd v1 -- sidecar-based meshes like Istio (AKA coordinated envoy) and API gateways like Kong are not direct competitors with Maesh, Linkerd v1 is. Is Maesh a newer imagining of what Linkerd v1 sought to do? Is it a better k8s-integrated solution?
I would say that L5d 2.0 would be the direct competitor. They are both: small, simple, opt-in, K8s centric, and support SMI.
Kubernetes is a container orchestration platform, AKA a way to deploy software on servers. If all of this sounds complex, it is, as it's Google-scale.
This looks interesting, but it's not clear to me if this supports TLS traffic to the daemon-set nodes running on each individual node. A key thing that I am looking at meshes for are last mile TLS encryption, with a appropriate sidecar.
For mTLS, the moment you want to have identity per service (as opposed to one cert across everything in the mesh), you need the security boundary to be at the pod level.