<p>I personally am a fan of <a href="https://github.com/mozilla/sops" rel="nofollow noreferrer">Mozilla SOps</a>, we've introduced it to two teams and it's gone down well both times, it has proven easy to implement both with local development and our CI/CD pipelines.</p>

<p>It has support for PGP/GPG to encrypt secrets but also supports Amazon KMS, GCP KMS and Azure KeyVault thus works well in an enterprise cloud-native infrastructure.</p>

CC BY-SA 4.0
2019-06-24T08:06:03.180Z
2019-06-24T08:06:03.180Z
Richard Slater
<p>If your use case is Kubernetes, I like <a href="https://github.com/bitnami-labs/sealed-secrets" rel="nofollow noreferrer">Sealed Secrets</a> </p>

<p>It is what <a href="https://www.weave.works/blog/storing-secure-sealed-secrets-using-gitops" rel="nofollow noreferrer">Weave Cloud</a> uses to store configuration and do GitOps. </p>

CC BY-SA 4.0
2019-06-25T22:35:35.497Z
2019-06-25T22:35:35.497Z
Ulukai
<p>I have spent a good amount of time lately looking into the <a href="https://github.com/godaddy/kubernetes-external-secrets" rel="nofollow noreferrer">GoDaddy open-source CRD called ExternalSecrets</a>. It's been pretty good to work with, it keeps the actual secret material in AWS Secrets Manager, and polls for changes. When a change is detected it creates/updates a Secret in your Kubernetes cluster. The only issue I've encountered is that you are mostly limited to using key/value pairs. </p>

CC BY-SA 4.0
2019-06-26T14:09:16.967Z
2019-06-26T14:09:16.967Z
Randy L
<p>git-crypt, git secret were found. What is your personal preference and why?</p>

<p>A couple of months ago, I have applied git-crypt. It was quite hard to set it up and the secrets are stored as binaries. I wonder whether git-secret is less cumbersome to set up. What other options are available?</p>

<git><encryption>
What options are available to encrypt the content of git repositories?
030
# What options are available to encrypt the content of git repositories?

(Asked by: username_0 on 2019-06-22)

git-crypt, git secret were found. What is your personal preference and why?

A couple of months ago, I have applied git-crypt. It was quite hard to set it up and the secrets are stored as binaries. I wonder whether git-secret is less cumbersome to set up. What other options are available?

**Tags:** git, encryption


---

## 3 answers

### Answer by username_1 on 2019-06-24. Score: 2 | Accepted answer

I personally am a fan of [Mozilla SOps](https://github.com/mozilla/sops), we've introduced it to two teams and it's gone down well both times, it has proven easy to implement both with local development and our CI/CD pipelines.

It has support for PGP/GPG to encrypt secrets but also supports Amazon KMS, GCP KMS and Azure KeyVault thus works well in an enterprise cloud-native infrastructure.


---

### Answer by username_2 on 2019-06-25. Score: 0

If your use case is Kubernetes, I like [Sealed Secrets](https://github.com/bitnami-labs/sealed-secrets)

It is what [Weave Cloud](https://www.weave.works/blog/storing-secure-sealed-secrets-using-gitops) uses to store configuration and do GitOps.


---

### Answer by username_3 on 2019-06-26. Score: 0

I have spent a good amount of time lately looking into the [GoDaddy open-source CRD called ExternalSecrets](https://github.com/godaddy/kubernetes-external-secrets). It's been pretty good to work with, it keeps the actual secret material in AWS Secrets Manager, and polls for changes. When a change is detected it creates/updates a Secret in your Kubernetes cluster. The only issue I've encountered is that you are mostly limited to using key/value pairs.


---

