#linkerd — Public Fediverse posts

#Linkerd 2.20 is here!

Highlights:
➡️ Reduces control plane memory usage by up to 85% under high pod churn.
➡️ Adds rate-limit-aware load balancing, automatically routing traffic away from services that are throttling requests.

Find out more 👉 https://bit.ly/4f7Hy5y

#Linkerd #ServiceMesh #Kubernetes #DevOps #CloudNative #InfoQ

Are you securing your agentic workloads — or just hoping for the best? 🦝 TCP-Talks #2169 with William Morgan covers how Linkerd and service mesh tackle real MCP security gaps. We'd love to know: is your team thinking about zero-trust for AI agents yet? Drop your thoughts and give it a listen!

https://www.thecloudpod.net/podcast/keep-the-raccoons-out-service-mesh-wiliam-morgan-buoyant/

#Linkerd #AgenticAI #CloudNative

Hot take from TCP-Talks #2169: service mesh isn't just infrastructure plumbing anymore. When AI agents start making autonomous calls via MCP, mTLS and zero-trust policy enforcement become your last real line of defense. William Morgan puts it plainly — the perimeter is gone, so identity at the workload level is everything.

https://www.thecloudpod.net/podcast/keep-the-raccoons-out-service-mesh-wiliam-morgan-buoyant/

#Linkerd #ZeroTrust #CloudNative

First thing I saw walking into the #KubeCon keynote hall this morning: William Morgan -ception! #Linkerd

Want to see #ServiceMesh? I'm demoing #Istio and #Linkerd at #DevOpsCon #London https://www.linkedin.com/company/devopsconference. Join us for "Service Mess to Service Mesh" and see how #Kubernetes #security works. Slides: https://robrich.org/slides/service-mess-to-service-mesh/rsa.html#/

Have you missed #KubeConEU in London this month?
I've got you covered!
Next week I'll run a #KubeCon recap live stream with my fellow #CNCF Ambassadors Kasper Borg Nissen (KubeCon Co-Chair) and William Rizzo (also a #Linkerd Ambassador).
Even if you've attended the event, you're bound to get cool insights 😉
And you can share your own on the live chat! and ask us questions!

🗓️ 22 April 2025, 11:00 CET, OpenObservability Talks:
🌐 https://youtu.be/JyxJOmOEBvQ

#cloudnative #cncfAmbassadors

Anyone else out there using #linkerd with #grafana Mimir and Alloy and having a hard time with overly chatty logs and metrics not being correctly stored? I have no idea what's happening.

Service Mess to #ServiceMesh. Do you need a ServiceMesh to guard your #kubernetes containers? Which one do you choose? We'll see a live demo of #Istio and #Linkerd. Join us in person at #DevOpsCon #SanDiego https://devopscon.io/microservices-software-architecture/server-mesh-security-istio-linkered, slides: https://robrich.org/slides/service-mess-to-service-mesh/

Service Mess to #ServiceMesh. Do you need a ServiceMesh to guard your #kubernetes containers? Which one do you choose? We'll see a live demo of #Istio and #Linkerd. Join us in person at #DevOpsCon #SanDiego https://devopscon.io/microservices-software-architecture/server-mesh-security-istio-linkered, slides: https://robrich.org/slides/service-mess-to-service-mesh/

New post on my blog. You can read it here: https://matduggan.com/the-time-linkerd-erased-my-load-balancer/
#kubernetes #linkerd #devops

Episode 2 of my new #podcast series is out, featuring William Morgan of #Buoyant, the vendor behind the #Linkerd #servicemesh. In February, Buoyant announced it would no longer be making a certain class of the project's code, called stable release artifacts, available for free to production users with more than 50 employees. In this interview, William discusses community reaction to that change and his view on #opensourcesustainability. #opensource. #OSS #CNCF

https://www.podbean.com/ew/pb-xb9ru-15cb865

@marcus_grant Yes, clarifying mutual expectations is good. If a contract on top of the license helps, so be it.

I'm not convinced it's primarily a legal issue: to this day, if you're a self-hosted user of #HashiCorp #FreeSoftware, you have no way to throw money at HashiCorp even if you want to.

Same with the #linkerd fiasco (https://github.com/cncf/toc/issues/1262): did Buoyant ever ask help from #CNCF or anyone before cutting off the supposed free-riders?

Maybe the VC playbook doesn't fit collaboration.

I've been thinking a lot about the #linkerd news today. I've been sitting on a pile of research and tutorials and am planning on running a PoC with it, but the news (and the responses around it) added a surprise bit of chaos to my plans.

I understand everybody's "but wait, opensource" anger, but I do think we're seeing lots and lots of companies and tools that were traditionally assumed as free making a point that actually it's _not_ free to do all of this work.

#Linkerd latest release 2.15 is out, and it's got a twist:
#Buoyant (the co behind the project) announced they "will no longer be producing #opensource stable releases",
but rather focusing on delivering Buoyant Enterprise for Linkerd (BEL).
This is a CNCF graduated project.
Yet largely with a single vendor behind it.
Disturbing.

While I’ll be following the #Linkerd / #CNCF drama with interest, this isn’t a rug pull like the #terraform license switch. #OpenSource means the source code is… well, open. That’s *all*. I’ve said it before: there’s no “spirit of open source” that always seems to put a ton of obligations on maintainers but never on users.

Doesn’t mean anyone has to be happy about the change, and I fully understand those who aren’t. But if it’s not in a license — OSS or commercial — it’s not an obligation.

Just published: #Linkerd paywall prompts online debate, #CNCF TOC review #OSS #servicemesh https://www.techtarget.com/searchitoperations/news/366571035/Linkerd-paywall-prompts-online-debate-CNCF-TOC-review

Companies with more than 50 employees using #Linkerd #servicemesh in production must pay Buoyant for stable releases starting in May. Open source users and analysts weigh in: https://www.techtarget.com/searchitoperations/news/366570820/Linkerd-service-mesh-production-users-will-soon-have-to-pay #OSS #CNCF

#linkerd has a great story for graceful start/stop of the sidecar. There's a tool cooled linkerd-await is automatically injected for graceful start. It can be explicitly used for graceful shutdown, but the API it uses is trivial to bake directly into code.
The current story on #istio is a mess of "add some shell commands to lifecycle hooks, and if you don't have those in your container, sad face".

for the curious.. the GKE (GCE) docs for #linkerd are here

https://linkerd.io/2.14/tasks/using-ingress/#gce

The GKE/GCE ingress is not installed in cluster, and the gce-ingress controller does not route traffic, it just provisions cloud resources. The paragraph is the sum total of the official docs, and that one paragraph is literal nonsense. (most blogs on the subject ignore ingress).

I've spent a week trying to get a decent production rollout of both #linkerd and #istio to #GKE, and neither is impressive.
Linkerd has gaps in the ingress story on GKE (and the docs are outright nonsense)
Istio is actually simpler (OMFG!), and has a better ingress story. But the graceful shutdown story is absolutely hilarious.
Not for the first time, I am baffled that anyone truly uses these things at scale.

#tech #kubernetes