kedacore/keda

Provide unified KEDA core configuration

Open

#1,330 opened on Nov 13, 2020

View on GitHubContributor guide
 (14 comments) (0 reactions) (1 assignee)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

A clear and concise description of what you want to happen.

Use-Case

When you run KEDA in a 12-factor environment, it's sometimes easier to configure it with environment variables (not commandline flags), in other cases, a pre-canned config file is more useful, and of course, we already have commandline flags, so those are certainly more useful to some people

I think we should support all 3 ways of configuring the KEDA controller (not necessarily the metrics API, but that could be considered)

Specification

  • Change the stdlib flags package usage to use viper, or a similar library that can draw configuration values from multiple sources

Contributor guide

Research direction
Explore the current command line flag setup and replace with viper to support environment variables and config files.
Tech stack
go
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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.
Clear
Prerequisites
GoGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75