snip.
← Back to Home ID: 47231
KubeFM @kube.fm
Jul 11, 08:32 AM

🗣️ Ben Poland discusses Jenkins Kubernetes plugin scaling limits - the plugin consistently failed around 1500-2000 pods with progressive slowdown that couldn't be resolved by adding more resources Watch the full episode: https://ku.bz/klBmzMY5-

🎤 Whisper Transcript (en) ⏱ 119s

"You mentioned starting with a single Jenkins instance that eventually grew to three. What were the specific limitations you hit with Jenkins as you scaled? Yeah, so, you know, we, like, basically we overloaded the single Jenkins instance. So when I started in 2020, we had, like you said, a single Jenkins controller. And there was, we ended up October of 2021. It sticks out of my brain because, you know, it was, it was a rough time. We finally hit the limits and it was a little unexpected. You know, I wish we had been a little bit better prepared. We knew that it was going to happen. It just, it all kind of came to crashing down faster than we expected. So luckily we had been preparing to deploy more Jenkins controllers. We kind of had a game plan in the works. And so we ended up having to accelerate that pretty quickly because all of our developers were not able to push code for a day or two. It was, it was rough. And, you know, you get into a situation with CI where the longer it's down, the more code people have written. And so when you do get it back up, everybody's pushing all stuff, they're like re-triggering builds. And, you know, you end up kind of with a thundering herd issue, right? But yeah, so we had that rough period. We ended up deploying a second Jenkins controller. Then we ended up with a third. And, you know, up until like late last year, early this year, we had over 20 Jenkins controllers to handle all of our CI load. And so, I mean, the issues that we're..."

💬 Discussion

KubeFM @kube.fm · Jul 9, 05:16 PM

🗣️ Ben Poland discusses Jenkins Kubernetes plugin scaling limits - the plugin consistently failed around 1500-2000 pods with progressive slowdown that couldn't be resolved by adding more resources Watch the full episode: https://ku.bz/klBmzMY5-

<div class="border-l-2 border-slate-800/60 pl-4 py-2 mt-3 ml-2"> <div class="flex items-start gap-2.5"> <!-- Avatar --> <img src="https://cdn.bsky.app/img/avatar/plain/did:plc:lmqvd7gy25wurfwyw64w6mnt/bafkreifvyywbx4difw4nb2tc7cdp3epvslcgpmn5c5ccwgykgoy2ba3tpm" class="w-6 h-6 rounded-full shrink-0 border border-slate-800" /> <!-- Comment Content --> <div class="flex-1 min-w-0"> <div class="flex items-center gap-2 mb-1"> <span class="text-xs font-bold text-slate-300">KubeFM</span> <span class="text-[10px] text-slate-500">@kube.fm</span> <span class="text-[9px] text-slate-600">· Jul 9, 05:16 PM</span> </div> <p class="text-xs text-slate-350 leading-relaxed break-words">This episode is brought to you by Testkube—where teams run millions of performance tests in real Kubernetes infrastructure. From air-gapped environments to massive scale deployments, orchestrate every testing tool in one platform. Check it out at https://ku.bz/lnxYK3s0L</p> </div> </div> <!-- Replies --> </div>