1"use strict";(self.webpackChunkkinvolk=self.webpackChunkkinvolk||[]).push([[2733],{32504:(e,n,a)=>{a.r(n),a.d(n,{assets:()=>o,contentTitle:()=>s,default:()=>u,frontMatter:()=>l,metadata:()=>r,toc:()=>d});var t=a(74848),i=a(28453);const l={slug:"2025/07/enabling-event-driven-autoscaling-with-the-new-keda-plugin-for-headlamp",title:"Headlamp: Enabling Event\u2011Driven Autoscaling with the New KEDA Plugin for Headlamp",draft:!1,image:"https://headlamp.dev/assets/images/splash-ac421269630ae2dfd8ddbc18a219942d.jpg"},s=void 0,r={permalink:"/blog/2025/07/enabling-event-driven-autoscaling-with-the-new-keda-plugin-for-headlamp",source:"@site/blog/2025-07-25-enabling-event-driven-autoscaling-with-the-new-keda-plugin-for-headlamp.md",title:"Headlamp: Enabling Event\u2011Driven Autoscaling with the New KEDA Plugin for Headlamp",description:"KEDA (Kubernetes Event-Driven Autoscaling) allows users to scale Kubernetes workloads based on external event sources like message queues, custom metrics, or HTTP requests. While KEDA is widely used for autoscaling based on real-world signals, working with KEDA resources like ScaledObjects and ScaledJobs often means relying on kubectl and editing YAML by hand.",date:"2025-07-25T00:00:00.000Z",tags:[],hasTruncateMarker:!1,authors:[],frontMatter:{slug:"2025/07/enabling-event-driven-autoscaling-with-the-new-keda-plugin-for-headlamp",title:"Headlamp: Enabling Event\u2011Driven Autoscaling with the New KEDA Plugin for Headlamp",draft:!1,image:"https://headlamp.dev/assets/images/splash-ac421269630ae2dfd8ddbc18a219942d.jpg"},unlisted:!1,prevItem:{title:"Headlamp: Introducing Headlamp AI Assistant",permalink:"/blog/2025/08/introducing-headlamp-ai-assistant"},nextItem:{title:"Headlamp: A One-click Local Experience with Headlamp Desktop",permalink:"/blog/2025/03/a-one-click-local-experience-with-headlamp-desktop"}},o={authorsImageUrls:[]},d=[{value:"Installing KEDA in your cluster\u200b",id:"installing-keda-in-your-cluster",level:2}];function c(e){const n={a:"a",h2:"h2",p:"p",...(0,i.R)(),...e.components};return(0,t.jsxs)(t.Fragment,{children:[(0,t.jsx)(n.p,{children:"KEDA (Kubernetes Event-Driven Autoscaling) allows users to scale Kubernetes workloads based on external event sources like message queues, custom metrics, or HTTP requests. While KEDA is widely used for autoscaling based on real-world signals, working with KEDA resources like ScaledObjects and ScaledJobs often means relying on kubectl and editing YAML by hand."}),"\n",(0,t.jsxs)(n.p,{children:["As part of a Linux Foundation (LFX) Mentorship project, we have built a Headlamp plugin that integrates a UI for viewing and managing KEDA resources directly in the Headlamp dashboard. The plugin was developed by ",(0,t.jsx)(n.a,{href:"https://github.com/adwait-godbole",children:"Adwait Godbole"}),", with guidance from the Headlamp team."]}),"\n",(0,t.jsxs)(n.h2,{id:"installing-keda-in-your-cluster",children:["Installing KEDA in your cluster",(0,t.jsx)(n.a,{href:"https://headlamp.dev/blog/2025/07/25/enabling-event-driven-autoscaling-with-the-new-keda-plugin-for-headlamp#installing-keda-in-your-cluster",title:"Direct link to Installing KEDA in your cluster",children:"\u200b"})]}),"\n",(0,t.jsx)(n.p,{children:(0,t.jsx)(n.a,{href:"https://headlamp.dev/blog/2025/07/25/enabling-event-driven-autoscaling-with-the-new-keda-plugin-for-headlamp",children:"Continue reading at headlamp.dev"})})]})}function u(e={}){const{wrapper:n}={...(0,i.R)(),...e.components};return n?(0,t.jsx)(n,{...e,children:(0,t.jsx)(c,{...e})}):c(e)}},28453:(e,n,a)=>{a.d(n,{R:()=>s,x:()=>r});var t=a(96540);const i={},l=t.createContext(i);function s(e){const n=t.useContext(l);return t.useMemo((function(){return"function"==typeof e?e(n):{...n,...e}}),[n,e])}function r(e){let n;return n=e.disableParentContext?"function"==typeof e.components?e.components(i):e.components||i:s(e.components),t.createElement(l.Provider,{value:n},e.children)}}}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.