You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
Hi,
i'm aware that Flux v2 exists, however i'm stuck with 1.14 of Kubernetes, so v2 is out of option AFAIK.
I'm trying to create a workflow using Flux, Helm Operator and Sops. I'm aware of #2804 and #3078 , however i thought, i could simply encrypt a HelmRelease resource locally, using sops -e --config .sops.yaml release.yaml > release.enc.yaml, commit that release.enc.yaml and let Flux decrypt it by using a .flux.yaml file. Like so roughly:
I believe this file is incomplete, however i'm having trouble understanding how to work with commandUpdated or patchUpdated exactly. I simply would like to decrypt the values: section of a HelmRelease, next i would expect Helm-Operator to discover the resource and apply it.
Nevermind, i figured it out, however i ended up using kustomize which i originally did not intend. .flux.yaml (release.enc.yaml contains values for a HelmRelease resource, encrypted with SOPS):
Hi,
i'm aware that Flux v2 exists, however i'm stuck with 1.14 of Kubernetes, so v2 is out of option AFAIK.
I'm trying to create a workflow using Flux, Helm Operator and Sops. I'm aware of #2804 and #3078 , however i thought, i could simply encrypt a
HelmRelease
resource locally, usingsops -e --config .sops.yaml release.yaml > release.enc.yaml
, commit thatrelease.enc.yaml
and let Flux decrypt it by using a.flux.yaml
file. Like so roughly:I believe this file is incomplete, however i'm having trouble understanding how to work with
commandUpdated
orpatchUpdated
exactly. I simply would like to decrypt thevalues:
section of aHelmRelease
, next i would expect Helm-Operator to discover the resource and apply it.values.yaml
i use for the Helm chart of Flux v1:Any help is appreciated.
The text was updated successfully, but these errors were encountered: