Flux: Question: Helm sealed secrets

Created on 26 Dec 2018  Â·  5Comments  Â·  Source: fluxcd/flux

Noob question:

I created a sealed secret for mysql username and another one for its password. However, I'm not sure how to feed it to mysql's helm chart. I actually think its not possible but want someone to tell me if I'm correct.

Looks like using values: on my HelmRelease will override the values.yaml. I can set mysqlUser and mysqlPassword but I have no idea how to get them from the actual secret. Would appreciate any advice.

question

Most helpful comment

It is possible, you can supply values from secrets using the HelmRelease.spec.valueFileSecrets array, here are the docs https://github.com/weaveworks/flux/blob/master/site/helm-integration.md#specvaluefilesecrets

You should create a single secret file with both username and password and supply that in the valueFileSecrets.

All 5 comments

It is possible, you can supply values from secrets using the HelmRelease.spec.valueFileSecrets array, here are the docs https://github.com/weaveworks/flux/blob/master/site/helm-integration.md#specvaluefilesecrets

You should create a single secret file with both username and password and supply that in the valueFileSecrets.

What a beauty. Thank you so much!

I've never seen this, helm-op or Flux are not deleting any kind of Kubernetes objects. Looks a like a bug in the Sealed Secrets controller, you should submit an issue to their repo.

Hi Stefan,

in the end it was my mistake as my 'rabbitmq' Secret name was clashing
with the one created by the HelmRelease :^/

I deleted the question (before I saw your reply) to avoid confusion, but thanks a lot for you quick response!

Cheers,
Andre

On Wed, 23 Jan 2019 at 14:10, Stefan Prodan notifications@github.com
wrote:

I've never seen this, helm-op or Flux are not deleting any kind of
Kubernetes objects. Looks a like a bug in the Sealed Secrets controller,
you should submit an issue to their repo.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/weaveworks/flux/issues/1616#issuecomment-456814619,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAa_SiYUYPs1p0A87b6wa-48IQxFYjWks5vGG1OgaJpZM4ZiD2t
.

I came here via google, and for others who do the same -

valueFileSecrets has now been replaced by valuesFrom secretKeyRef
https://docs.fluxcd.io/projects/helm-operator/en/stable/helmrelease-guide/values/#secrets

Was this page helpful?
0 / 5 - 0 ratings