kedacore/keda

Provide support for SecretProviderClass as identity provider in TriggerAuthentication

开放

#1,407 创建于 2020年12月9日

 (4 条评论) (0 个反应) (0 位负责人)Go (1,457 个派生)auto 404
authfeature-requesthelp wantedneeds-discussionstale-bot-ignore

仓库指标

星标
 (10,372 个星标)
PR 合并指标
 (平均合并 8天 8小时) (30 天内合并 94 个 PR)

描述

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.

贡献者指南