Enterprise power without enterprise complexity. Linkerd adds security, observability, and reliability to any Kubernetes cluster. 100% open source, CNCF graduated, and written in Rust.
Linkerdの外部リンク
Linkerdさんが再投稿しました
Missed last week's Code RED episode? Dash0's Mirko Novakovic chatted with Buoyant CEO William Morgan about all things service mesh, including what agentic workloads in production mean for a mesh like Linkerd. Listen to their full conversation: https://hubs.ly/Q04fgCZ70 #Kubernetes #OpenSource #Linkerd #CloudNative #ServiceMesh #MCP
Linkerdさんが再投稿しました
The ultimate cloud native escape room is now available on demand! This is your chance to solve the "Kube-napping! Phippy's Abduction on the Canals" mystery. Phippy, the beloved CNCF mascot, has vanished, a victim of the nefarious Unknown Controller. Her liveness probe is failing, and time is running out. Are you ready to deploy your Kubernetes and Linkerd skills to follow the metrics, read the traces, and debug the deployments in this high-stakes cloud native challenge? Start your mission today → https://lnkd.in/eFYZmDMt #Kubernetes #Linkerd #CloudNative #EscapeRoom #ServiceMesh The characters Phippy, Captain Kube, Zee, Linky, Hazel, Cappy, Izzy, Keddy, Owlina, Obee, Tai, and Tiago are owned by The Linux Foundation, on behalf of the Cloud Native Computing Foundation (https://lnkd.in/eMViyt6i).
Linkerdさんが再投稿しました
Most teams working on Kubernetes do not need a service mesh. But the ones that do need it badly. So, what is a service mesh, and do you need one? Buoyant CEO William Morgan came on my podcast this week to break it down. A service mesh is an infrastructure layer between your applications and the network. In a Kubernetes environment, it gives platform teams control at the service-to-service level, with things like retries, timeouts, circuit breaking, mutual TLS, authorization policy, and HTTP/gRPC instrumentation built in. While traditional networking mostly answers questions like: did the packets get there, how many, and between which IPs? A service mesh works at a higher level of abstraction. It understands that service A is talking to service B, and gives you security, reliability, and visibility at that layer. Whether you need one comes down to trade-offs. If you are running a serious platform where reliability, security, and multi-cluster communication really matter, a service mesh can make a lot of sense. If you have a single cluster and a relatively lightweight application, it may be more than you need. That is what makes service mesh an engineering decision, not a default checkbox. Listen to the episode below ⬇️
Linkerdさんが再投稿しました
We are excited to announce that The AI Kubernetes Show is officially becoming a regular, biweekly podcast! 🚀 Join host William Morgan as we continue to move beyond prompt engineering to tackle the fundamental shifts that GenAI is bringing to platform engineering. In the first episode of the new season with Michael Lieberman, CTO at Kusari (going live next Wednesday, May 6), we chat about supply chain security in the age of AI. Also look forward to great conversations with Scott Feinberg (Schonfeld); Evaline J. (IBM); Blake R. (Imagine Learning), Abdel SGHIOUAR (Google), Ronald Petty (RX-M, LLC), and many more great guests. Read our blog post for details on the new season and how to subscribe: https://hubs.ly/Q04dVfVR0 #TheAIKubernetesShow #AI #Kubernetes #PlatformEngineering #Podcast
Linkerdさんが再投稿しました
Up next on Service Mesh Academy: Help! Something’s Wrong With My Mesh: A Linkerd Troubleshooting Checklist with Ehsan Shirazi. You've deployed Linkerd, your services are meshed, and mTLS is running. Then something looks off. Traffic errors you can't immediately explain. A pod that isn't injected. A certificate warning you weren't expecting. Knowing where to look, and in what order, is the difference between a five-minute triage and a two-hour incident. In this session, we'll walk through a practical troubleshooting checklist built from real-world Linkerd production deployments: how to read linkerd check output, how to diagnose proxy injection failures without assumptions about how your team configured it, the three distinct traffic error signatures and how to interpret them, and how to recognize when the destination controller is the real culprit behind FailFast errors at scale. ✦ When: Thursday, May 14, 9 am PT | 12 pm ET | 6 pm CET ✦ Register at: https://hubs.ly/Q04dJGK10 #Kubernetes #OpenSource #Linkerd #CloudNative #ServiceMesh #ServiceMeshAcademy
Linkerdさんが再投稿しました
The Kube-napping investigation is now live online! Cluster Detectives, if you weren't able to attend Buoyant's escape room party at KubeCon Amsterdam, or if you couldn't complete the challenges, you can finalize your mission now on your laptops. The ultimate cloud native escape room, Kube-napping! Phippy's Abduction on the Canals, is now available online! The dark deployment still lingers over Amsterdam, and Phippy’s liveness probe depends on your skills. Use your Kubernetes and Linkerd expertise to follow the traces, find the logs, and debug the deployments to solve this service mesh abduction mystery. Start the virtual Kube-napping investigation now ☞ https://hubs.ly/Q04b52gS0 #KubeNapping #SavePhippy #Linkerd #Kubernetes #CloudNative #EscapeRoom
Linkerdさんが再投稿しました
In this episode of Coffee and Open Source, host Isaac Levin sits down with William Morgan, CEO of Buoyant, creators of Linkerd. They chat about the evolution of the cloud native ecosystem, from the early days of Linux to the modern complexities of microservices and platform engineering. William shares the raw, behind-the-scenes journey of building a sustainable business around open source, including the controversial decision to move toward a commercial stable release model to ensure the long-term health of the Linkerd project. Listen to the full podcast here: https://hubs.ly/Q049LK9r0 #Kubernetes #Linkerd #OpenSource
Linkerdさんが再投稿しました
You've deployed Linkerd. Your services have mTLS, your traffic is observable, and your platform team is sleeping better at night. So what comes next? Buoyant Cloud, a feature of Buoyant Enterprise for Linkerd, delivers health monitoring, alerting, and deep operational visibility across all your clusters. In this Service Mesh Academy, we'll explore what Buoyant Cloud puts at your fingertips: traffic success rates, failure breakdowns, golden metrics for your workloads, events, and more. Join us for a live demo of what operational visibility really looks like.
Linkerdさんが再投稿しました
Great to see the CNCF project updates running before the #KubeCon keynotes! I always enjoy hearing about #Dapr from 🎩 Marc Duiker and Linkerd from William Morgan 📈
Linkerdさんが再投稿しました
The official Escape Room Party track (+ lyrics) by DJ Linky 🤩 (Register for the party if you haven't yet ☞ https://lnkd.in/dW2uMdjY) Something’s wrong inside the cluster. Latency rising, logs all flustered. Pods are failing, traffic spiking. Unknown Controller now is striking. Metrics screaming in the night, Tracing packets left and right. Linky says, “We’ve got a clue." Service mesh is watching you. Follow the traces, Read the flow. Something’s breaking, Deep below. We won’t panic, We won’t flip, Stabilize the service mesh. Save Phippy, save the day. Debug the cluster, find the way. Kubernetes in the zone, Mesh is routing, not alone. Save Phippy, lock the vault. Fix the outage, find the fault. Trace it, patch it, ship it fast, Service mesh will hold it fast. Rolling updates, zero trust, Memory safe, no buffer bust. Rust inside the data plane, Latency dropping once again. Multi-cluster, zone-aware, Traffic's shifting everywhere. From the ingress to the pod, Observability is God. Check the metrics, Read the graph. Is it liveness? Is it a path? Scale it, route it, Fix the flow. Mesh is running, go go go! Save Phippy, save the day, Engineers will lead the way. Packets dancing through the mesh, Production-ready, fresh. Save Phippy, breach the vault, No more errors, no more faults. Kubernetes standing tall, Service mesh just saved us all. Trace. Route. Scale. Deploy. Trace. Route. Scale. Deploy. Linky’s watching. Cluster steady. Mesh engaged. Production-ready. Save Phippy, save the night. Debug heroes in the light. From the logs to service mesh, We restore, and we refresh. Save Phippy, case complete. Unknown Controller tastes defeat. Vault unlocked, the crowd goes wild, Cluster stable. Chaos exiled. Listen to the track ☞ https://lnkd.in/eRv6MsqM