<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>KEDA on Selenium</title><link>https://deploy-preview-2615--selenium-dev.netlify.app/tags/keda/</link><description>Recent content in KEDA on Selenium</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 27 Feb 2026 01:42:26 +0700</lastBuildDate><atom:link href="https://deploy-preview-2615--selenium-dev.netlify.app/tags/keda/index.xml" rel="self" type="application/rss+xml"/><item><title>Selenium Grid 4.41.0: What's New and Why It Matters</title><link>https://deploy-preview-2615--selenium-dev.netlify.app/blog/2026/selenium-grid-4-41-deep-dive/</link><pubDate>Sun, 22 Feb 2026 00:00:00 +0000</pubDate><guid>https://deploy-preview-2615--selenium-dev.netlify.app/blog/2026/selenium-grid-4-41-deep-dive/</guid><description>&lt;p>We are excited to ship Selenium Grid &lt;strong>4.41.0&lt;/strong> 🎉 — and this might be one of impactful releases in recent memory. Whether you are running Grid in a bare-metal lab, a Docker Compose stack, or a sprawling Kubernetes cluster, this release brings something meaningful for you. From a brand-new &lt;strong>Dynamic Grid for Kubernetes&lt;/strong>, a powerful &lt;strong>Session Event API&lt;/strong>, to smarter video recording and a rock-solid Distributor, let&amp;rsquo;s dig in.&lt;/p>
&lt;hr>
&lt;h2 id="1-dynamic-grid-now-native-on-kubernetes">1. Dynamic Grid, Now Native on Kubernetes&lt;/h2>
&lt;p>The headline feature of 4.41.0 is unambiguous: &lt;strong>Dynamic Grid now runs natively inside Kubernetes clusters&lt;/strong> (&lt;a href="https://github.com/SeleniumHQ/selenium/pull/17092">selenium#17092&lt;/a>, &lt;a href="https://github.com/SeleniumHQ/docker-selenium/pull/3082">docker-selenium#3082&lt;/a>).&lt;/p></description></item><item><title>Scaling a Kubernetes Selenium Grid with KEDA</title><link>https://deploy-preview-2615--selenium-dev.netlify.app/blog/2022/scaling-grid-with-keda/</link><pubDate>Fri, 19 Aug 2022 00:00:00 +0000</pubDate><guid>https://deploy-preview-2615--selenium-dev.netlify.app/blog/2022/scaling-grid-with-keda/</guid><description>&lt;h2 id="the-issue">The Issue&lt;/h2>
&lt;p>If you have any experience with Selenium Grid and Kubernetes you will probably
run into an issue with scaling. Kubernetes (K8S) works wonders for scaling up and
down applications based on their CPU and Memory usage, but it is not so
straightforward when it comes down to applications like Selenium Grid.&lt;/p>
&lt;p>The issue is described quite well in &lt;a href="https://sahajamit.medium.com/spinning-up-your-own-auto-scalable-selenium-grid-in-kubernetes-part-2-15b11f228ed8">this blog post&lt;/a>.
But in short, the Horizontal Pod AutoScaler (HPA) that is built into
Kubernetes checks (by default) for resource consumption to determine
if a deployment needs to be scaled up or down. This becomes an issue
for Selenium Grid for a couple reasons:&lt;/p></description></item></channel></rss>