kedacore/keda

Integration with the Cluster Autoscaler

Open

#637 opened on Feb 20, 2020

View on GitHubContributor guide
 (27 comments) (20 reactions) (0 assignees)Go (1,457 forks)auto 404
feature-requesthelp wantedneeds-discussionstale-bot-ignore

Repository metrics

Stars
 (10,372 stars)
PR merge metrics
 (PR metrics pending)

Description

Today KEDA can indirectly influence cluster autoscaling by causing the HPA to schedule too many pods so the cluster autoscaler kicks in and adds nodes. A common ask is to have KEDA potentially poke the cluster autoscaler even earlier the same way it pokes HPA before CPU + Memory hit. Not sure what integrations make this possible today, but would be a nice feature to be able to set some cluster threshold or something, or some way to describe driving cluster scale in addition to HPA scale.

Contributor guide

Research direction
Examine how KEDA currently interacts with the Kubernetes Horizontal Pod Autoscaler (HPA) and explore potential hooks or APIs provided by the Cluster Autoscaler. Look for existing community discussions or proposals on this topic.
Tech stack
go
Domain
backendinfrastructureclouddevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Kubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30