-
Notifications
You must be signed in to change notification settings - Fork 135
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Christian Hernandez <[email protected]> Co-authored-by: Jesse Suen <[email protected]> Co-authored-by: Kent Rancourt <[email protected]> Co-authored-by: Nicholas Morey <[email protected]>
- Loading branch information
1 parent
a253fe3
commit 1c2692d
Showing
1 changed file
with
59 additions
and
0 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,59 @@ | ||
--- | ||
title: Roadmap | ||
Description: Kargo Roadmap | ||
--- | ||
|
||
# Roadmap | ||
|
||
Over a series of releases, Kargo's maintainers intend to establish and settle into a predictable, but yet to be determined release cadence. | ||
|
||
:::caution | ||
This roadmap is subject to change at any time, for the most up to date information, please see the [GitHub Project](https://github.com/akuity/kargo/milestones) | ||
::: | ||
|
||
## v0.2.0 | ||
|
||
| Name | Type | Description | | ||
| ---- | ---- | ----------- | | ||
| Freight and Warehouse CRDs | feature | Freight will change from being a property of a `Stage`, to being its own CRD. The source of where promotable `Freight` comes from will be known as a `Warehouse`. | | ||
| GitHub PR-Based Promotion | feature | Support for pull request based promotions, which do not complete until the underlying PR is closed. | | ||
| Kargo Render | breaking change | Bookkeeper to be rebranded as Kargo Render -- a Kargo child project for rendering manifests. | | ||
|
||
|
||
## v0.3.0 | ||
|
||
| Name | Type | Description | | ||
| ---- | ---- | ----------- | | ||
| Analysis | feature | Ability to execute user-defined analysis steps to qualify or disqualify Freight for further promotion. | | ||
| Improved RBAC | feature | Map SSO user identities to Kubernetes ServiceAccounts. Predefined ServiceAccount/Role/RoleBinding per project based on persona. | | ||
| Freight Production Rules/Filters | feature | Git repository subscriptions options to constrain conditions under which new Freight is produced. | | ||
|
||
## v0.4.0 | ||
|
||
| Name | Type | Description | | ||
| ---- | ---- | ----------- | | ||
| Project Management | feature | Introduce Project CRD to simplify onboarding and project lifecycle management. Support aggregate information at the project status level. Additional `PromotionPolicy` options. Credential management via CLI and UI. | | ||
|
||
## v0.5.0 | ||
|
||
| Name | Type | Description | | ||
| ---- | ---- | ----------- | | ||
| Promotion Mechanism Extensibility | feature | User-defined promotion mechanisms. | | ||
|
||
## v0.6.0 .. v0.n.0 | ||
|
||
| Name | Type | Description | | ||
| ---- | ---- | ----------- | | ||
| Freight Enrichment | feature | Enhance Freight metadata for improved insight into Freight contents and the expected result of promoting a piece of Freight to a given environment. This data will be exposed to the UI and CLI tools. | | ||
| `Improved Microservice Support | feature | Filters for Freightlines (for example, filter by Warehouse). Add the ability to merge parallel Freightlines at a control flow Stages. | | ||
| `kargo init` | feature | Addition of an `init` sub-command to the Kargo CLI for streamlining project / pipeline creation. | | ||
| Standalone Image Writeback` | feature | Write back image changes without having to subscribe to an image repository. | | ||
| PromotionPolicy Improvements | feature | Add the ability to "freeze" Stages to prevent promotions. | | ||
|
||
## Criteria for 1.0.0 Release | ||
|
||
Maintainers will consider cutting a stable v1.0.0 release once: | ||
|
||
* Confident in API stability. (No further breaking changes anticipated.) | ||
* No critical, "show-stopping" bugs remaining in the backlog. | ||
* Observing evidence of successful community adoption (of beta releases) in production environments |