layer5 VS istio

From My PR being merged, working on UI, Upgrading Gatsby v2 to v3 for which I had to learn a bit about GraphQL, how Gatsby Plugins work (PR) to me shifting to CI/CD Issues, writing blogs, learning golang(for mesheryctl issues) to having the most amazing as well as exciting 1-1 call with Lee Calcote, Founder & CEO of Layer5 to discuss about my interests/aims and some future ideas/goals of the projects, the journey has been amazing and I hope it will be the same or much more exciting in the future 💯 Also, I have to thank Nikhil Ladha as well as other members of the community for constantly guiding and mentoring me 🍻

Istio is an open-source service mesh that makes managing, securing, and shaping all traffic and communication between your microservices – and adding observability, too – possible, without ever writing code for any of this – no matter how your distributed architecture is deployed.

The closest I've come to finding a solution is Orchestrating GPU-accelerated streaming apps using WebRTC, their code is available on GitHub. I don't fully understand their approach, I believe it depends on Istio.

Istio is an Orchestration & Management / Service Mesh project. With a service mesh, traffic between services is handled at a platform level. This way, reliability, observability, and security features can be tackled here and provided uniformly across all services, instead of being delegated to developers to include in their code. Istio has become the second Incubating CNCF project with the most stars and with most contributors this year.

Tools in the DevOps ecosystem I have explored : Devtron, Spinnaker, Argo CD, Istio. Great UX: Devtron, Argo CD Bad UX : Istio , Spinnaker

Open source API Gateway (Apache APISIX and Traefik), Service Mesh (Istio and Linkerd) solutions are capable of doing traffic splitting and implementing functionalities like Canary Release and Blue-Green deployment. With canary testing, you can make a critical examination of a new release of an API by selecting only a small portion of your user base. We will cover the canary release next section.

OIDC OAuth for k8s authorization had nothing to do with AAA in your app.Nginx as an ingress or an API gateway is pretty much obsolete - you have to pick an API Gateway with an external Auth support, like Contour and it's auth server.More advanced service meshes, like istio has a built-in authz policies for JWT handling.Keep in mind that with the introduction of API Gateway spec, it's really important to pick the most mature solution out of the bunch. It's especially crucial, after 1.26 release, because current SIG can port the auth policies from service meshes directly into kubernetes admission, like it happened already with OPA & Kyverno policies.

I have experimented with other service meshes and I was able to get up to speed quickly: Linkerd = 1 day, Istio = 3 days, NGINX Service Mesh = 5 days, but Consul Connect service mesh took at least 11 days to get off the ground. This is by far the most complex solution available.

I just "scratched the surface" of what's possible with CUE in this post. It has been attracting attention and being adopted in projects such as Istio, which it uses to generate OpenAPI schemes and CRDs for Kubernetes and Dagger. It is a tool that can be very useful for several projects, mainly due to its data validation power. And as a replacement for YAML, for my personal joy :D

You mean "all I could find was Kubernetes, Docker, TerraForm infrastructure as code language, Istio service mesh, gVisor security layer, Prometheus metrics service, Argo CD..." Oh, and almost every tool on https://landscape.cncf.io/