Istio

Istio 1.23 (https://lnkd.in/eCBp7fsp) went out last week 🎉 A big SHOUTOUT to all contributors of Istio that helped directly or directly with the project. The success of Istio could not happen without all of you! Would appreciate you show your support on Linkedin in addition to Slack!! 💕

At #OSSummitEU this week in Vienna? Don't miss these Istio sessions!

IMO, Istio is the second coolest CNCF project. I'm more than happy to help curate this NA co-located event!

Want to meet the Co-creator of Istio and gRPC? Join us at the 6th #K8SUG #UK Meetup on September 17th at Civo Tech Junction! This is your chance to engage with Louis Ryan, Co-creator of Istio and gRPC, and CTO at solo.io. Connect with fellow tech enthusiasts and advance your cloud-native knowledge. Don’t miss this opportunity to learn from one of the best in the field! 🚀 Event details: https://lnkd.in/ev2x2gAC Registration (free): https://lnkd.in/e97ffUPh See you there! #K8SUG #TechJunction #Istio #Kubernetes #CloudNative K8SUG - the Most Active K8s + AI Meetup

Very excited about speaking at Open Source Summit Europe in Vienna next Monday! I'll host 2 sessions below plus an "Ask Me Anything" session around Cloud Native Computing Foundation (CNCF), Service Mesh and Istio also on Monday. Please say HI to me!!

Humbled to serve as an co-chair for IstioDay NA 2024! You can explore the schedule here: https://lnkd.in/eE9TGx96. Stay tuned for deeper dives on the talks and speakers!

Attention #TeamCloudNative! The KubeCon + CloudNativeCon All-Access Pass is the only way in to ALL 15 CNCF-Hosted Co-Located Events, taking place on Nov 12! ⭐ The schedules are all LIVE! Dive in + take a look: https://hubs.la/Q02NL4YL0 📍 Get your pass + join us in Salt Lake City: https://hubs.la/Q02NL0gD0 #KubeCon #CloudNativeCon #Kubernetes #K8s #CloudNative #OpenSource #OpenSourceSoftware #OpenSourceDevelopment #OpenSourceCommunity #OSS #CNCF #CloudNativeComputingFoundation #events #linux #software

Calling all Kubernetes users: if Istio ambient happens to improve your application latency, can you please share? 🙏 Lin Sun explained in her blog 2 reasons why this happened with one service from our famous Bookinfo app, check it out: https://lnkd.in/gQ7F7eSG

To be or not to be? Service mesh with Sidecars or sidecarless? During my PhD studies, Paul Townend and I, found out that there is no unified architecture for service meshes and even there is an ongoing discussion in the community around that (see the paper link in the comments). But which one is the best option to choose? As always, my answer would be "it depends". It depends on various factors such as the in-house knowledge, resources, requirements and many others. Let's take Istio for example, Istio offers both Ambient and traditional sidecar mode. In sidecar mode there will be an Envoy proxy deployed on each pod. And in Ambient mode, we will have a proxy called ZTunnel on each node responsible for L4 things. In Ambient mode we can even bypass Linux networking stack by using eBPF for routing. And if we are interested to have L7 stuff, we could use **per namespace** waypoint proxies. All of these can bring different benefits to the table. The very first thing is that Ambient mode is still in Beta and classic traffic management APIs (virtual service, destination rules etc) remain at Alpha, while Sidecar mode is stable for some years now. We can achieve almost the same features in both modes but with different latency and security level. The Ambient mode has lower latency but it's also less secure. As in Ambient mode, each node agent has only the keys for workloads on that node, while in sidecar mode each workload has its own keys. The most important point is that sidecar mode requires more resources than Ambient mode. With all this, what would you choose and why? To me, if we are in an environment where different services are owned by different teams, and we want to give our application developers more ability, Istio sidecar mode seems more reasonable. And if our application is latency-sensitive and we have limited budget and we want to restrict application developers Ambient mode seems more reasonable. Any thoughts? **Important Note**: In the slides, it's mentioned the Sidecar mode is less secure, which is wrong, please consider it the other way around. Want to see more posts like this? Follow #istio_tutorial for an upcoming series on Istio! --- Are you interested in #cloudnative projects such #kubernetes and #istio like me? Click my name + follow + 🔔 so you don’t miss out!

Shoutout to The New Stack for the great writeup about our newest Istio v1.23 🙌 🙌🙌 https://lnkd.in/eCBp7fsp