kedacore/keda

Provide support for SecretProviderClass as identity provider in TriggerAuthentication

Open

#1,407 opened on Dec 9, 2020

View on GitHubContributor guide
 (4 comments) (0 reactions) (0 assignees)Go (1,457 forks)auto 404
authfeature-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

Based on this discussion https://github.com/kedacore/keda/discussions/1387#discussioncomment-176572 I would like to be able to use a SecretProviderClass to mount secrets in a deployment that is scaled using KEDA.

Currently when the deployment scales to 0 the SecretProviderClass is destroyed because nothing is using it, but when KEDA is trying to scale the deployment back up, it fails to find the secrets necessary for the deployment (since the SecretProviderClass hasn't been reconstructed yet).

Specification

  • Allow KEDA to create the SecretProviderClass before trying to scale the deployment.

Contributor guide

Research direction
Investigate how to integrate SecretProviderClass with TriggerAuthentication to ensure secrets are available before scaling up, possibly by creating the SecretProviderClass as a prerequisite or watching for its creation.
Tech stack
gokubernetes
Domain
backenddevops
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.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
KubernetesGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50