-
Notifications
You must be signed in to change notification settings - Fork 25
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #177 from vmware-tanzu/feature/blog
Landing!
- Loading branch information
Showing
4 changed files
with
122 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,120 @@ | ||
--- | ||
# /* | ||
# | Protect your secrets, protect your sensitive data. | ||
# : Explore VMware Secrets Manager docs at https://vsecm.com/ | ||
# </ | ||
# <>/ keep your secrets… secret | ||
# >/ | ||
# <>/' Copyright 2023–present VMware, Inc. | ||
# >/' SPDX-License-Identifier: BSD-2-Clause | ||
# */ | ||
|
||
title: Keep Your Secrets… Secret | ||
layout: post | ||
prev_url: / | ||
permalink: /blog/keep-your-secrets/ | ||
--- | ||
|
||
by [Volkan Özçelik](https://github.com/v0lkan); last updated on August 15, 2023. | ||
|
||
## Introducing VMware Secrets Manager | ||
|
||
![Welcome to the future of secrets management. (image generated by Midjourney)](/assets/VSecM-1.png) | ||
|
||
In the ever-evolving landscape of cloud-native applications, secrets management | ||
is critical to ensuring sensitive information’s security and integrity. While | ||
several solutions are available, the recent shift in Hashicorp’s licensing towards | ||
a Business Source License (*BSL*) has raised concerns and sparked discussions | ||
within the community. | ||
|
||
As the lead architect of [**VMware Secrets Manager** (**_VSecM_**)](https://vsecm.com/), | ||
I’d like to take this opportunity to introduce our solution, which offers a robust, | ||
flexible, and **permissive** alternative to Hashicorp’s Vault. | ||
|
||
> **⭐️ Star Us on GitHub ⭐️** | ||
> | ||
> If you find value in our approach and want to help others discover this outstanding | ||
> technology, **[star our GitHub repository](https://github.com/vmware-tanzu/secrets-manager)**. | ||
> Your support helps increase visibility and encourages more collaboration and | ||
> innovation within the community. | ||
{: .block-tip } | ||
|
||
## A New Licensing Landscape | ||
|
||
Hashicorp’s decision to adopt a Business Source License has been viewed by some | ||
as a restrictive move. The BSL, unlike open-source licenses, imposes certain | ||
limitations and conditions that may not align with the needs and values of all | ||
organizations and developers. | ||
|
||
In contrast, VMware Secrets Manager is licensed under the BSD 2-Clause License, | ||
a permissive open-source license that encourages collaboration, innovation, | ||
and freedom of use. | ||
|
||
## VMware Secrets Manager: A Closer Look | ||
|
||
**VSecM** is designed with modern developers and DevOps professionals in mind. | ||
Here’s why it stands out: | ||
|
||
* **Ease of Use**: With a [**Quickstart Guide**](https://vsecm.com/docs/quickstart/), | ||
intuitive [**CLI**](https://vsecm.com/docs/cli/?ref=zerotohero.dev), and | ||
developer-friendly [**SDK**](https://vsecm.com/docs/sdk/), **VSecM** | ||
simplifies secrets management without compromising security. | ||
* **Kubernetes Is a First-Class Citizen**: **VSecM** seamlessly integrates with | ||
Kubernetes, leveraging [**SPIRE**](https://spiffe.io/docs/latest/spire-about/) | ||
for authentication and offering flexible secret storage and transformation options. | ||
* **Community Engagement**: We believe in open collaboration and community-driven | ||
development. Our [**Contributing Guide**](https://vsecm.com/docs/contributing/) | ||
invites developers to get involved, ask questions, and contribute to the project. | ||
* **Secure by Default**: **VSecM** offers advanced security features, including | ||
encryption, manual master secret setting, and integration with various backing | ||
stores. | ||
|
||
## Join the Future of Secrets Management | ||
|
||
**VMware Secrets Manager** is more than just a tool; it’s a community-driven project | ||
that aims to redefine secrets management in a cloud-native world. We invite you to | ||
explore **VSecM**, contribute to its growth, and join us in shaping the future of | ||
secure and resilient applications. | ||
|
||
Whether you’re a developer looking to contribute or an organization seeking a | ||
flexible and secure solution for secrets management, **VSecM** offers a welcoming | ||
and innovative platform. | ||
|
||
### This is Just the Beginning: A Vision for the Future | ||
|
||
At **VMware Secrets Manager**, we believe in continuous innovation and growth. | ||
Our [**roadmap**](https://vsecm.com/docs/roadmap) is a testament to our commitment | ||
to delivering cutting-edge solutions that meet the evolving needs of the cloud-native | ||
community. | ||
|
||
Here's a glimpse of what's on the horizon: | ||
|
||
* **Stability and Usability Enhancements**: Upcoming releases focus on improving | ||
stability, documentation, build automation, and overall user experience. | ||
* **Innovative Features**: From Secretless VSecM to machine-readable logs, | ||
performance improvements, and large-scale secret ingestion, we're pushing the | ||
boundaries of what's possible in secrets management. | ||
* **Integration and Compatibility**: Future iterations include integration with | ||
AWS KMS, Azure Key Vault, Google Cloud KMS, and even HashiCorp Vault, expanding | ||
the reach and compatibility of VSecM. | ||
* **Community Development and Collaboration**: We're investing in community | ||
development efforts, multi-cluster secret federation, and creating abstractions | ||
to make cloud integrations easier. | ||
|
||
Our roadmap is not just a plan; it’s a promise to our users and contributors that | ||
we have a lot planned for the future of **VMware Secrets Manager**. | ||
|
||
We’re excited about the journey ahead and invite you to be a part of it. | ||
|
||
> **⭐️ Star Us on GitHub ⭐️** | ||
> | ||
> If you find value in our approach and want to help others discover this | ||
> outstanding technology, **[star our GitHub repository](https://github.com/vmware-tanzu/secrets-manager)**. | ||
> Your support helps increase visibility and encourages more collaboration and | ||
> innovation within the community. | ||
{: .block-tip } | ||
|
||
### Help Us Shape the Future | ||
|
||
[**Start your journey with VMware Secrets Manager today**](https://vsecm.com/) | ||
and unlock the potential of cloud-native secrets management. |