kamus VS helm-secrets

I tried using the idea at https://stackoverflow.com/questions/54190837/helm-install-in-kuberneres-error-this-command-needs-2-arguments-release-name but it didn't help. Can you spot what I am doing wrong? Thank you.

Kamus may represent a compromise between Sealed Secrets and SOPS. It was created especially for the GitOps use case and includes an operator. It can either manage the key material itself or obtain it from the KMS of the cloud providers. Another special feature is that Kamus encrypts secrets directly for an application. They are then decrypted by the application itself or by an init container. This means that the unencrypted secret is never present on the API server and ideally also not in an environment variable with in the container.

helm plugin install https://github.com/databus23/helm-diff helm plugin install https://github.com/aslafy-z/helm-git helm plugin install https://github.com/jkroepke/helm-secrets

I use Helm secrets which integrates Mozilla Sops to handle secrets in my Helm charts.

Use Helm Secrets.

ArgoCD users would have to build container images with SOPS baked in using Helm chart extensions or Kustomize extensions. Flux allows configuring sops directly into the Flux manifests.

There is also the helm secrets plugin, which can also be used in ArgoCD with manual configuration.

Not sure if this is applicable for your use case, but you could use helm-secrets to fetch remote value files from https or git: https://github.com/jkroepke/helm-secrets/wiki/Values

$ helm plugin install https://github.com/jkroepke/helm-secrets --version v3.14.0

https://github.com/jkroepke/helm-secrets powered by sops

SOPS is great, and there are a lot of GitOps tools that either integrate with SOPS directly or make it relatively painless to integrate into your workflow, e.g. helm-secrets.

SOPS and helm-secrets: https://github.com/jkroepke/helm-secrets