This is a page where we publish our approximate roadmap for VMware Secrets Manager for Cloud-Native Apps. Note that this is not a commitment to deliver any of the features listed here, and that the roadmap is subject to change at any time without notice.
Whenever we release a new version of VMware Secrets Manager, we will update this page, and also the changelog to reflect the changes.
One-Year Window
This page will only contain information about the next 12 months of the project. We will update the roadmap every release, and remove the completed items from the list, and add a new iteration at the end of the list.
Jun 29, 2024 - Sep 30, 2024
This iteration is about increasing coverage. We will focus on unit tests.
Our goal is to reach at least 50% coverage.
In addition, we are targeting to fix certain low-hanging bugs and improve stability.
Here is a list of issues that are candidate for VSecM vHydra.
Oct 01, 2024 - Oct 28, 2024
In this iteration, we will focus on adding use cases and tutorials, along with any stability and security improvement that may come our way.
Here is a list of issues that are candidate for VSecM vIndus.
Oc 29, 2024 - Nov 25, 2024
This iteration will be about adding more features that may be immediately useful around VSecM Sentinel CLI.
Here is a list of issues that are candidate for VSecM vLupus.
Nov 26, 2024 - Jan 6, 2025
This iteration is about SDKs and KMS integration.
Here is a list of issues that are candidate for VSecM vMensa.
Jan 07, 2024 - Feb 03, 2024
The overall theme of this iteration is issues labeled as enhancing the system’s scalability, high availability (HA), and integration capabilities. Key areas of focus include improving HA modes for various components, enabling state federation and synchronization with external storage systems, enhancing documentation, and expanding the flexibility of key management through integration with cloud Key Management Services (KMS) and databases.
These efforts aim to make VMware Secrets Manager more robust, reliable, and easier to integrate with other systems and environments.
This iteration is about visibility and metrics. We’ll create a /stats
and a
/health
endpoint for VSecM Safe among other observability improvements.
Here is a list of issues that are candidate for VSecM vNorma.
Feb 04, 2024 - Mar 03, 2024
This iteration is centered around enhancing the system’s capabilities in high availability, scalability, and integration. Key areas include:
Here is a list of issues that are candidate for VSecM vOrion.
Mar 04, 2024 - Mar 31, 2025
This iteration centers on enhancing the system’s scalability, high availability, and integration capabilities. Key areas include:
Here is a list of issues that are candidate for VSecM vPerseus.
Apr 01, 2024 - Apr 28, 2025
This iteration aims at enhancing security, workflow, and documentation. The open issues include:
Security Enhancements: Use a separate VSecM Safe to store root keys instead of
a Kubernetes secret, improving security by isolating critical keys from the
main application infrastructure.
Workflow Improvements: Ensuring the project includes an automated test suite that provides at least 90% statement coverage, which aims to improve the reliability and maintainability of the codebase.
Documentation Updates:: Documenting the VSecM Sentinel OIDC authentication feature, which will help users understand and implement this feature more effectively.
Here is a list of issues that are candidate for VSecM vReticulum.
Apr 31, 2025 - May 26, 2025
This iteration revolves around enhancing functionality, improving integration capabilities, and expanding test coverage. The key areas include:
Enhanced Integration and Configuration: Ability to configure SPIRE’s key manager in Helm charts.
Workflow and Automation Improvements:
Use Cases and Examples:
Here is a list of issues that are candidate for VSecM vSagittarius.
May 27, 2025 – Jul 31 2025
This iteration focuses on enhancing security, improving integration and workflow, and providing new features for better user experience. Here are the main points:
Here is a list of issues that are candidate for VSecM vTelescopium.
Aug 01, 2025 – Aug 28 2025
This iteration is focused on enhancing the system’s security, improving integration capabilities, and refining user experience. Key points include:
PKCS#11
interface to
secure root keys.Here is a list of issues that are candidate for VSecM vUrsa.
Aug 29, 2025 – Sep 25 2025
This is mainly a security-focused iteration. Here are the main points:
ValidatingAdmissionWebhook
to ensure clusterspiffeid
s
and clusterspiffeid
templates have the correct format.Here is a list of issues that are candidate for VSecM vVirgo.
Sep 26, 2025 – Oct 32 2025
This is a “catch all” that contains all remaining documented future plans. We will create new iterations from it as the time gets closer.
Here is a list of issues that are candidate for VSecM vUrsa.
May 23, 2024 - Jun 19, 2024
The sole focus of this iteration was increasing unit test coverage and adding more integration tests.
We also introduced improvements too; however, stability will be our main focus.
Here is a list of issues that are candidate for VSecM vGemini .
Apr 25, 2024 - May 22, 2024
This iteration will was about stability and documentation updates.
We also introduced a lot of flexibility such as ability to use custom namespaces, trust domains, and regex-based SPIFFEID validation.
Here is a list of issues that are candidate for VSecM vFornax .
Mar 28, 2023 - Apr 24, 2024
This iteration was mostly about security and stability.
Here is a list of issues that were closed in vEridanus.
Feb 29, 2023 - Mar 27, 2023
To automate things and be able to dynamically follow issues better, from this point on we started labeling them and share the GitHub filter here.
This iteration was mainly focused on demos and documentation.
Here is a list of issues that were closed in vDraco.
Feb 01, 2024 - Feb 28, 2024
This iteration was focused on improving how VMware Secrets Manager logs and reports errors. We will also focus on improving the performance of the VMware Secrets Manager website.
Secret
less VSecM: Ability to use VMware Secrets Manager without relying
on Kubernetes Secret
s. This will allow users to use VMware Secrets Manager
without having to create Kubernetes Secret
s at all–even for the root keys.Secret
s without necessarily associating them
with a workload.Sep 12, 2023 - Jan 31, 2024
This was a relatively longer release because due to the “time-stop” effect of the holiday season, the majority of the core contributors will be spending quality time with their loved ones and recharging their batteries for the upcoming year.
This release will be more about enhancing deployment workflows, testing automation and CI/CD pipelines. We will also focus on improving the overall user experience.
Aug 15, 2023 - Sep, 11, 2023
This was a stability-focused release. We focused on fixing bugs, improving stability, and improving workflows and CI/CD pipelines. We also created missing documentation and generated new video tutorials that feature the current version of VMware Secrets Manager.
Check out the release notes to learn more about what has been added, changed, and fixed in this release.