From 2b4d0e9f3d73eb1f6dd4a3f99c64fb836d1faa69 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Volkan=20O=CC=88zc=CC=A7elik?= Date: Sat, 5 Aug 2023 09:43:58 -0700 Subject: [PATCH] created an initial roadmap MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit we can discuss and fine-tune it later. Signed-off-by: Volkan Özçelik --- docs/_pages/0001-roadmap.md | 75 ++++++++++++++++++++++++---- docs/assets/gitbook/rouge/github.css | 4 +- 2 files changed, 66 insertions(+), 13 deletions(-) diff --git a/docs/_pages/0001-roadmap.md b/docs/_pages/0001-roadmap.md index 3e5e63ac..8b9748e7 100644 --- a/docs/_pages/0001-roadmap.md +++ b/docs/_pages/0001-roadmap.md @@ -59,64 +59,117 @@ Here is a high-level list of features that we plan to deliver in this release: 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. -* TBD +* `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 master keys. +* Adding subcommands to **VSecM Sentinel**’s `safe` command to make it easier + to use, and reduce unnecessary flags and arguments. +* Static code analysis. +* More automation and tests. ## VSecM v0.23.0 (*codename: Cassiopeia*) **Oct 10, 2023 – Nov 6, 2023** -* TBD +This iteration will be 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. + +* Better, machine-readable logs. +* Preventing log tampering. +* Performance improvements on the website. +* More use-case video lectures. ## VSecM v0.24.0 (*codename: Draco*) **Nov 7, 2023 – Dec 4, 2023** -* TBD +This iteration will be focused on making **VMware Secrets Manager** able to +ingest large amounts of secrets, without crashing or slowing down. + +* Stream manipulation: Ability to ingest large amounts of secrets; also + ability to ingest longer secrets. +* More automation. ## VSecM v0.25.0 (*codename: Eridanus*) **Dec 5, 2023 – Jan 1, 2024** -* TBD +In this iteration, our focus will be in-memory usage of **VSecM** and also making +the **VSecM Sidecar** more robust. + +* Option for **VSecM** to run in-memory; without having to rely on any backing store. +* Option for the **VSecM Sidecar** to kill the container when the bound secret changes. ## VSecM v0.26.0 (*codename: Fornax*) **Jan 2, 2024 – Jan 29, 2024** -* TBD +This is an iteration focused on code stability, and community development. + +* Validation and guardrails around VSecM-managed SVIDs. +* Community development efforts. +* Taking a stab at multi-cluster secret federation. ## VSecM v0.27.0 (*codename: Gemini*) **Jan 30, 2024 – Feb 26, 2024** -* TBD +We’ll create abstractions around certain **VMware Secrets Manager** components +to make further cloud integrations easier. + +* Creating custom resources (`ClusterVSecMId`) for better abstraction. +* Improving usability and developer experience. ## VSecM v0.28.0 (*codename: Hydra*) **Feb 27, 2024 – Mar 25, 2024** -* TBD +This iteration will be about providing access to **VSecM Sentinel** through +OIDC authentication. We will also focus on various compatibility issues before +we dive into cloud integration in the upcoming iterations. + +The goals in this iteration could be a stretch and based on the workload of +the core maintainers, we might have to push some of these goals to the next +iteration, thus impacting the overall roadmap. + +* OIDC authentication. +* Using Redis as a shared backing store. +* Ability to deploy VSecM to any SPIFFE-compatible cluster that has agents + that provide SPIFFE Workload API. ## VSecM v0.29.0 (*codename: Indus*) **Mar 26, 2024 – Apr 22, 2024** -* TBD +This iteration will be about integrating **VMware Secrets Manager** with +**AWS KMS**. + +* AWS KMS Integration ## VSecM v0.30.0 (*codename: Lupus*) **Apr 23, 2024 – May 20, 2024** -* TBD +This iteration will be about integrating **VMware Secrets Manager** with +**Azure Key Vault**. + +* Azure Key Vault Integration ## VSecM v0.31.0 (*codename: Mensa*) **May 21, 2024 – Jun 17, 2024** -* TBD +This iteration will be about integrating **VMware Secrets Manager** with +**Google Cloud KMS**. + +* Google Cloud KMS Integration ## VSecM v0.32.0 (*codename: Norma*) **Jun 18, 2024 – Jul 15, 2024** -* TBD \ No newline at end of file +This iteration will be about integrating **VMware Secrets Manager** with +**Hashicorp Vault**. + +* Hashicorp Vault Integration \ No newline at end of file diff --git a/docs/assets/gitbook/rouge/github.css b/docs/assets/gitbook/rouge/github.css index 1e25f42f..7e7b393d 100644 --- a/docs/assets/gitbook/rouge/github.css +++ b/docs/assets/gitbook/rouge/github.css @@ -51,7 +51,7 @@ color: #888888; } .highlight .gp { - color: #555555; + color: #aaaaaa; } .highlight .gs { font-weight: bold; @@ -184,7 +184,7 @@ font-weight: bold; } .highlight .nn { - color: #555555; + color: #aaaaaa; } .highlight .nt { color: #edc910;