Secret Sync alpha release!

[ramizpolic]

🎉 New Project - Secret Sync 🎉

We are excited to announce the alpha release of Secret Sync, a project designed to streamline secret synchronization.

Secret Sync exposes a generic way to interact with external secret storage systems like HashiCorp Vault and provides a set of API models to interact and orchestrate the synchronization of secrets between them.

🌟 Features

• Simple integration with a variety of secret storage systems
• User-friendly API to facilitate interaction between different stores
• Pipeline-like syntax for defining synchronization actions on a secret level
• Advanced templating capabilities for transforming secrets

To get familiarized, find the Getting Started guide which will walk you through how to use Secret Sync in a GitOps way.

❓ What's next?
We are actively working on consolidating our APIs and expanding the list of supported secret storage providers.
Check out our Roadmap to see the new features we are working on.

🗣️ We are looking for feedback!
Your insights are crucial to us. You can support us with your feedback, bug reports, and feature requests by responding to this announcement, or opening an issue.

This release marks another important milestone for Bank-Vaults in our mission to simplify and enhance secret management in the Cloud Native ecosystem.

[ernadh]

Congratulations! This is an important milestone!

Do we provide a mechanism to synchronize Kubernetes Secret resource with Vault?

[sagikazarmark]

Although we may add Kubernetes secret support at some point, for Vault to k8s Secret synchronization we recommend checking External Secrets

[ernadh]

Yeah, the motivation behind the question was mostly to be able to tell folks to phase out External Secrets as part of secret-sync adoption. :)

[sagikazarmark]

I think it depends on the use case, but the way I see it, ESO and BV complement each other: ESO works well when you go all in on Kubernetes secrets (which is your decision but brings a number of issues of its own).

BV is the way to go when you don't want to use k8s secrets, but don't want to hardcode Vault into your application either. BV is the service mesh of secret management. :P

Some buffoon actually did a talk on this: https://presentations.cncf.io/presentations/automate-secret-rotation-in-kubernetes-then-get-out-of-the-way/

[ernadh]

You got me with BV being the service mesh of secret management! Nice talk too!