acoustic-carpenter-78188
07/10/2023, 6:17 PM$ cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: Secret
metadata:
name: flyte-binary-inline-config-secret
namespace: flyte
type: Opaque
stringData:
202-database-secrets.yaml: |
database:
postgres:
password: <DB_PASSWORD>
203-storage-secrets.yaml: |
storage:
stow:
config:
access_key_id: <S3_ACCESS_KEY>
secret_key: <S3_SECRET_KEY>
204-auth-secrets.yaml: |
auth:
appAuth:
selfAuthServer:
staticClients:
flytepropeller:
client_secret: <CLIENT_SECRET_HASH>
EOF
2. Reference the newly created secret in .Values.configuration.inlineSecretRef in values.yaml as follows:
configuration:
inlineSecretRef: flyte-binary-inline-config-secret
The above secrets will be merged into the base configuration created by the chart, and values will be available, as expected, to the Flyte platform.
OIDC/Internal Client secrets
1. Create an external secret containing the client secret values:
$ cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: Secret
metadata:
name: flyte-binary-client-secrets-external-secret
namespace: flyte
type: Opaque
stringData:
client_secret: <INTERNAL_CLIENT_SECRET>
oidc_client_secret: <OIDC_CLIENT_SECRET>
EOF
2. Reference the newly created secret in .Values.configuration.auth.clientSecretsExternalSecretRef in values.yaml as follows:
configuration:
auth:
clientSecretsExternalSecretRef: flyte-binary-client-secrets-external-secret
flyteorg/flyte
GitHub Actions: build-and-push-sandbox-bundled-image
✅ 11 other checks have passed
11/12 successful checksacoustic-carpenter-78188
07/10/2023, 6:17 PMacoustic-carpenter-78188
07/10/2023, 8:47 PM