kedacore/keda

KEDA for multi-cluster use-case

Open

#1,587 opened on Feb 9, 2021

View on GitHubContributor guide
 (29 comments) (6 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

Support workload expansion on multiple clusters

Use-Case

HTTP/gRPC based workloads have first class support for multi-cluster expansion by several multi-cluster ingress controllers. But queue workers are more challenging for multi-cluster scheduling. The list of use-cases when multi-cluster is useful is as following:

  • Support huge workloads that can't fit single cluster's resources
  • Seamless cluster and infrastructure version upgrade
  • BCP

Specification

it would be great to have a prototype for Kubernetes Federation that enables ScaledObjects/Jobs integration with FederatedDeployment/Jobs

Contributor guide

Research direction
Investigate KEDA's current architecture and Kubernetes Federation (kubefed) to design a prototype for multi cluster ScaledObject/Job integration.
Tech stack
go
Domain
backendinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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.
Needs investigation
Prerequisites
GoKubernetesKEDA
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30