Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sops guide: Add note that only encrypted yaml files are supported #779

Closed
mapster opened this issue Jan 26, 2021 · 2 comments · Fixed by fluxcd/kustomize-controller#469
Closed

Comments

@mapster
Copy link

mapster commented Jan 26, 2021

The formulation of the Mozilla Sops guide doesn't make it clear that the Kustomize-controller can only (?) decrypt sops-encrypted yaml files included in a kustomization.yaml. For instance a sops-encrypted env-file included through the secretGenerator-field in a kustomization.yaml won't be decrypted.

@davinkevin
Copy link

I leverage all the capacity of the secretGenerator, and especially files and envs. Thank to that, we can modify files in their native format (and not embedded in yaml). With sops, we ensure those secrets are encrypted. This is the same problem for helm charts with some values sops encrypted used inside an helmCharts generator.

So, this is the main case why I can't use flux, in pro an perso context. @stefanprodan, do you think something could be done for this, especially because kustomize way to managed secret will lead to this case a lot now.

Thank you 👍

@davinkevin
Copy link

Thank you @stefanprodan. Can’t wait to test it !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants