Carsten Klaus
04/25/2023, 4:35 PMprovider: s3
providerConfig:
s3:
disableSSL: true
v2Signing: true
endpoint: <http://XXXXXXXXXX:9000>
authType: accesskey
accessKey: XXXXX <<<<-------
secretKey: XXXXXXXXXXXXXXX <<<<---
Of course I cant write it into the config file directly. Is there a straightforward way I dont see here? Like Env Vars?
Thanks in advance!David Espejo (he/him)
04/25/2023, 4:42 PMYee
Ketan (kumare3)
Carsten Klaus
04/26/2023, 9:07 AMhelm install flyte-backend \
flyteorg/flyte-binary \
--namespace flyte \
--values flyte/values.yaml
The values.yaml
file contains every configuration detail, unfortunately the S3 Keys as plain text.
Hi @Yee
My values.yaml
looks very similar, its not exactly the sandbox, but its basically the same.
Imagine I do a git push
into our repo everyone could see the secrets as plain text, big No No!. So I need a way to set some values during runtime.
My first idea were environment variables (did not work)
accessKey: ${S3_ACCESS_KEY}
My second approach was a helm interpolation
accessKey: {{ .Values.accessKey }}
Unfortunately this also did not work because the values.yaml is not interpolatable.
Hi @Ketan (kumare3)
Is that possible to inject k8s secrets in the values.yaml?Ketan (kumare3)
Yee
Carsten Klaus
05/03/2023, 9:05 AMhelm repo list
(flyteorg https://flyteorg.github.io/flyte)
Which of the following charts (folders) was installed here?
https://github.com/flyteorg/flyte/tree/master/chartsDavid Espejo (he/him)
05/03/2023, 10:48 AMhelm list --namespace <your-namespace>
jeev
values.yaml
file, and use extra volume / extra volume mount to mount overrides from a pre-created secret object. will also need another secret object that will need to be propagated to dataplane namespaces, and added to task pods' envFrom
in the primary container spec via a pod template likely.David Espejo (he/him)
05/04/2023, 10:41 AM