From 3619926b548f32fd46658e8eca9e52d442001100 Mon Sep 17 00:00:00 2001 From: "yini.gao@schibsted.com" Date: Fri, 15 Mar 2024 13:28:50 +0100 Subject: [PATCH] add 'create' key for adminOauthClientCredentials Signed-off-by: yini.gao@schibsted.com Signed-off-by: Yini --- charts/flyte-core/templates/common/secret-auth.yaml | 2 +- charts/flyte-core/values.yaml | 7 +++++-- 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/charts/flyte-core/templates/common/secret-auth.yaml b/charts/flyte-core/templates/common/secret-auth.yaml index 50290357d8e..3fa7a257b2d 100644 --- a/charts/flyte-core/templates/common/secret-auth.yaml +++ b/charts/flyte-core/templates/common/secret-auth.yaml @@ -1,4 +1,4 @@ -{{- if .Values.secrets.adminOauthClientCredentials.enabled }} +{{- if .Values.secrets.adminOauthClientCredentials.create }} apiVersion: v1 kind: Secret metadata: diff --git a/charts/flyte-core/values.yaml b/charts/flyte-core/values.yaml index 0319b3bacae..fb40a402b59 100755 --- a/charts/flyte-core/values.yaml +++ b/charts/flyte-core/values.yaml @@ -430,10 +430,13 @@ deployRedoc: false secrets: adminOauthClientCredentials: - # -- If enabled is true, helm will create and manage `flyte-secret-auth` and populate it with `clientSecret`. - # If enabled is false, it's up to the user to create `flyte-secret-auth` as described in + # -- If enabled is true, helm will populate `flyte-secret-auth` with `clientSecret`. + # If enabled is false, helm will not populate `flyte-secret-auth`. + # If create is true, helm will create the `flyte-secret-auth`. + # If create is false, it's up to the user to create `flyte-secret-auth` as described in # https://docs.flyte.org/en/latest/deployment/cluster_config/auth_setup.html#oauth2-authorization-server enabled: true + create: true clientSecret: foobar clientId: flytepropeller