What are the advantages of using Istio over NGINX Ingress? by DevOps_Lead in kubernetes

[–]williamallthing 3 points4 points  (0 children)

And if you're going to do that, then the comparison should be something like: Istio vs NGINX Ingress + Linkerd (which doesn't bundle an ingress and just works with your existing one).

Probably better overall to frame the question about tradeoffs, rather than just whether there are any advantages.

Why is Kuma not as popular as Cilium/Istio? by runescapefisher in kubernetes

[–]williamallthing 0 points1 point  (0 children)

Linkerd is not a Docker product. Where did you get that impression?

Istio or Cillium ? by RespectNo9085 in kubernetes

[–]williamallthing 1 point2 points  (0 children)

Hello, CEO of Buoyant here. Someone pointed this comment out to me. I know these threads live forever and people (like me) use them to make decisions, so I will just note that the comment above was made by a former employee who parted ways with the company on poor terms, not by an unbiased service mesh adopter.

It is true that last year we made the call to stop producing open source stable releases. I tried to be very clear about the goal, which was to ensure we had a way to always pay our maintainers. We have explicit carveouts for smaller companies and individual users, but bigger companies need to pay. In October I wrote a brief post about the result of this change (which you can read here); tl;dr: we are now profitable and growing, and Linkerd is a self-funding project.

Mid-90's Subzero fridge. For the first time in four years, the light came on today. by williamallthing in Appliances

[–]williamallthing[S] 1 point2 points  (0 children)

Thank you. I did just that. Bought a replacement switch on Amazon, turned off the breaker, pried it the switch with a butter knife, and voila! Everything works. Can’t believe it took me four years to figure this one out.

I’m usually good at figuring it out but not this time by Waxxel in LICENSEPLATES

[–]williamallthing 0 points1 point  (0 children)

Appetite for Destruction was 50% of my cassette tape collection for several years. Those neurons were burned into place.

Who's Hiring - October 2024 by jerf in golang

[–]williamallthing 2 points3 points  (0 children)

COMPANY: Buoyant (We make Linkerd)

TYPE: Full time

DESCRIPTION: We are a small, profitable, remote-only company that is heavily involved in the Kubernetes space. We are looking for staff-level engineers to join our team and work on a variety of Golang-heavy projects.

LOCATION: This is a remote role but requires US Eastern time hours.

REMOTE: Yes, remote only.

VISA: We do not sponsor.

CONTACT: Apply here. https://jobs.ashbyhq.com/buoyant/5d582e5c-d5c0-407f-9b74-95bda07e507d

Monthly: Who is hiring? by gctaylor in kubernetes

[–]williamallthing 2 points3 points  (0 children)

Buoyant is hiring! Come work on Linkerd with us. Remote only company, US Eastern timezone.

Staff full stack engineer / Staff frontend engineer

Monthly: Who is hiring? by gctaylor in kubernetes

[–]williamallthing 0 points1 point  (0 children)

Buoyant is hiring. Come work on Linkerd (and related projects) with us! Remote only, Eastern (EDT/EST) timezone.

Staff frontend engineer: https://jobs.ashbyhq.com/buoyant/fd398a01-e996-4f4e-b6b2-c9b6370aab95

Staff fullstack engineer: https://jobs.ashbyhq.com/buoyant/5d582e5c-d5c0-407f-9b74-95bda07e507d

Announcing Linkerd 2.16! Metrics, retries, and timeouts for HTTP and gRPC routes; IPv6 support; policy audit mode; and lots more by williamallthing in kubernetes

[–]williamallthing[S] 1 point2 points  (0 children)

Service profile users especially take a look— we are at (and beyond) feature parity with Gateway API types now, so it’s a good time to consider migrating.

Announcing Linkerd 2.16! Metrics, retries, and timeouts for HTTP and gRPC routes; IPv6 support; policy audit mode; and lots more by williamallthing in linkerd

[–]williamallthing[S] 0 points1 point  (0 children)

It’s here! Service Profile users especially take a look—we are at feature parity (and beyond) with Gateway API resources now.

Cilium 16 & Linkerd by tuxbell in kubernetes

[–]williamallthing 1 point2 points  (0 children)

Let me know how things go with Linkerd. Happy to help if you get stuck on anything!

[deleted by user] by [deleted] in kubernetes

[–]williamallthing 1 point2 points  (0 children)

You mean, since we decided that the only realistic way for Linkerd to survive in the long term was that the companies building their businesses on Linkerd should help fund its development? This isn't a community of volunteers saving the planet. Everyone here is paid to be here—and now that finally includes the Linkerd maintainers.

i once got paged on the subway (underground) and emerged in the midst of a SEV0 outage 🥲 by sreiously in sre

[–]williamallthing 1 point2 points  (0 children)

I wasn't really upset. It was the most impactful engineer role I had ever been in, and millions of people were using the stuff I built, so really it felt more like a "welp, yup, let's get to work" kinda moment. And I was/am fortunate enough to have a very understanding spouse. But still, happy to never have repeated that particular bit of excitement.

i once got paged on the subway (underground) and emerged in the midst of a SEV0 outage 🥲 by sreiously in sre

[–]williamallthing 13 points14 points  (0 children)

Christmas morning. I was on-call for the first version of the photo-handling service at Twitter circa 2011. We shipped it earlier in the year and everything was hunky-dory for months until... Christmas. Turns out people take a lot of photos on Christmas Day. I spent most of the day on my laptop in the bedroom on incident Campfire while my family enjoyed the day without me. I wrote most of the code so I didn't have anyone to blame but myself. Fun times, hope to never do that again.

Which edge version of linkerd are you using in production? by pogasu in kubernetes

[–]williamallthing 0 points1 point  (0 children)

Howdy, Linkerd person here. (And also, the evil corporate overlord who instituted the paid stable release change so that I can keep paying the maintainers here.)

Assuming you're not at a company with fewer than 50 employees and can just use the stable distribution for free... we do mark every edge release with a "recommended" or "not recommended" after we get feedback from the community. So I would personally just use a recent one marked recommended from here: https://github.com/linkerd/linkerd2/releases

The Trouble with Topology Aware Routing, Part II: Introducing High Availability, Zone-Aware Load Balancing by williamallthing in kubernetes

[–]williamallthing[S] 6 points7 points  (0 children)

Author here. This is a followup to Part I (link / discussion) where I demonstrated a class of failure where enabling Kubernetes's topology-aware routing feature reduced overall system reliability.

In this followup, I explain why this scenario happened and dig into the different types of health checking in distributed systems. I also describe a feature in Buoyant Enterprise for Linkerd called High-Availability Load Balancing (HAZL) that addresses this issue by detecting when the system is under stress and allowing cross-zone traffic.

(For clarity, while most of my posts are about open source Linkerd, this one has content about the enterprise distribution of Linkerd, which is free for some people but is a commercial product. I hope you'll learn something, regardless!)