Skip to content

Releases: akuity/kargo

v0.3.0-alpha.1

22 Nov 16:51
72b21f7
Compare
Choose a tag to compare
v0.3.0-alpha.1 Pre-release
Pre-release

What's Changed

New Contributors

Full Changelog: v0.2.0...v0.3.0-alpha.1

v0.2.1

17 Nov 00:56
ebe8018
Compare
Choose a tag to compare

What's Changed

Bug fixes:

  • Fixed auto-promotions
  • Prevented Kargo Render failures from bleeding git repo credentials into logs
  • Gave controller permission to patch warehouses
  • Fixed broken "promote to subscribers" button (the "truck button") in UI

Full Changelog: v0.2.0...v0.2.1

v0.2.1-rc.2

16 Nov 21:41
d11cd1a
Compare
Choose a tag to compare
v0.2.1-rc.2 Pre-release
Pre-release
make ci work for semver-ish branch names (#1131)

Signed-off-by: Kent <kent.rancourt@gmail.com>

v0.2.1-rc.1

16 Nov 17:42
d59e2d6
Compare
Choose a tag to compare
v0.2.1-rc.1 Pre-release
Pre-release
Merge branch 'main' into v0.2.x

v0.2.0

14 Nov 20:03
047ff02
Compare
Choose a tag to compare

What's Changed

First-Class Freight

Anyone who has been following what we've been doing already knows that "freight" -- a set of references to one or more versioned artifacts -- is an important concept in Kargo. Important as it is, it was nevertheless not represented as its own top-level resource type in Kargo v0.1.0. Freight existed only within the status of various Stage resources. This made it onerous and inefficient for Stage resources, when reconciled, to locate available freight (i.e. other states to which they could be transitioned).

In v0.2.0, we've promoted (pardon the pun) freight to a first-class concept represented by a new custom resource type -- Freight. This small architectural pivot makes it much easier to get a piece of freight, list freight, or query for freight available to a given stage (i.e. freight that has qualified in an upstream stage). The CLI has, of course, evolved along with this change, and it is now possible to get and list Freight.

Warehouses

In Kargo v0.1.0, with freight being the more nebulous concept that it was, production of new freight was tightly-coupled to stages with direct subscriptions to Git, container image, and/or Helm chart repositories.

With freight now having becoming a first-class concept with its own resource type, Kargo v0.2.0 has decoupled the production of new freight from the stages by introducing a warehouse concept, which is also represented by its own custom resource type -- Warehouse.

Warehouse resources now encapsulate subscriptions to one or more Git, container image, and/or Helm chart repositories. Those repositories are polled each time a Warehouse resource is reconciled, at times resulting in the production of new Freight resources. Stages that may previously have subscribed directly to various repositories subscribe indirectly now by subscribing to a warehouse instead.

The CLI and UI have, of course, evolved around this new concept as well. It is possible to use either to "refresh" a warehouse, thereby forcing the repositories to which it subscribes to be polled on-demand.

Most importantly, we believe the warehouse concept introduces a logical place to introduce more fine-grained control over repository subscriptions and the conditions under which new freight is produced as we begin work on v0.3.0.

Bookkeeper Rebranded as Kargo Render

Many Kargo users may not have known about Bookkeeper. Bookkeeper is Kargo's little brother and integrates very well with Kargo. In short, Bookkeeper makes short work of rendering stage-specific configuration in a GitOps repository into plain YAML manifests that it stores in stage-specific branches. Under the hood, it uses your choice of Kustomize or Helm and configuration that lives in the GitOps repository, right alongside the Kustomize overlays or Helm charts on which it operates.

We feel so strongly that Kargo works best when used with Bookkeeper that we've now rebranded Bookkeeper as Kargo Render.

Visit https://kargo-render.akuity.io to learn more!

Other Notable Changes

  • Admin tokens now have a longer default TTL.
  • Promotions are reconciled faster.
  • Reduced (go mod) dependency on Argo CD and GitOps Engine -- part of an overall effort to eliminate those dependencies entirely so we can upgrade Kubernetes freely as needed.
  • Numerous:
    • Small enhancements
    • Documentation improvements
    • Process improvements

New Contributors

We would also like to thank the following first-time community contributors! Their interest in the project and their efforts demonstrate that what we're aspiring to is bigger than Akuity, and that Kargo is out to solve real pain points that are felt throughout the entire GitOps community!

Full Changelog: v0.1.0...v0.2.0

v0.2.0-rc.2

14 Nov 19:27
047ff02
Compare
Choose a tag to compare
v0.2.0-rc.2 Pre-release
Pre-release
fix fig step in release process (#1105)

Signed-off-by: Kent <kent.rancourt@gmail.com>

v0.2.0-rc.1

13 Nov 18:14
db85549
Compare
Choose a tag to compare
v0.2.0-rc.1 Pre-release
Pre-release
cli: add get + delete warehouse commands (#1087)

Signed-off-by: Kent <kent.rancourt@gmail.com>

v0.1.1-rc.2

28 Oct 07:41
1c2692d
Compare
Choose a tag to compare
v0.1.1-rc.2 Pre-release
Pre-release

What's Changed

New Contributors

Full Changelog: v0.1.1-rc.1...v0.1.1-rc.2

v0.1.1-rc.1

17 Oct 14:18
b30125e
Compare
Choose a tag to compare
v0.1.1-rc.1 Pre-release
Pre-release
chore(deps): bump curlimages/curl from 8.3.0 to 8.4.0 (#965)

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

v0.1.0

19 Sep 20:32
9203c78
Compare
Choose a tag to compare
Add `get promotions` command to CLI (#790)

Signed-off-by: Sunghoon Kang <hoon@akuity.io>
Co-authored-by: Kent Rancourt <kent.rancourt@gmail.com>