v0.8.0-rc.2

feat: add v0.7.x --> v0.8.x upgrade logic (#2309)

Signed-off-by: Hidde Beydals <[email protected]>
Signed-off-by: Kent Rancourt <[email protected]>
Co-authored-by: Kent Rancourt <[email protected]>

v0.8.0-rc.1

feat(controller): irsa support (#2235)

Signed-off-by: Blake Pettersson <[email protected]>
Signed-off-by: Kent Rancourt <[email protected]>
Co-authored-by: Kent Rancourt <[email protected]>

v0.7.1

fix(promo): notice changes to Argo CD source updates (#2157)

Signed-off-by: Hidde Beydals <[email protected]>

v0.7.0

💥  Akuity and our valued collaborators are excited to unveil Kargo v0.7.0!

As with the last several releases, this one is so jam-packed with changes and features that we're going to focus here on just a few highlights and invite you to consult the full changelog if you want to learn more.

Upgrade Path

If you are upgrading from v0.6.0, you're all set.

There is no upgrade path from versions prior to v0.6.0.

ECR and Google Artifact Registry Support

🆕  New Features

The community spoke and we listened.

Things weren't going so well for users with Warehouses subscribed to ECR and Google Artifact Registry (or GCR) repositories.

ECR offers no option at all for accessing repositories using long-term credentials, which was making it quite impossible to furnish Kargo with a username and password/token in the form of a Kubernetes Secret.

While Google Artifact Registry does offer an option for accessing repositories with long-term credentials, that option is not recommended by Google -- or by Kargo.

With all of this in mind, we've added new options for authenticating to these registries:

• Provide an AWS access key ID + secret access key or a GCP service account key and Kargo will use them to obtain short-lived tokens.

  These are "lowest common denominator" options that one might settle for if using ECR or Google Container Registry but running Kargo outside of EKS or GKE, respectively.

• Support for obtaining short-lived tokens without involving any Secret at all by leveraging:

  • EKS Pod Identity

  • GKE Workload Identity Federation

You can read more about these new options in our documentation.

Improved Artifact Discovery and Manual Freight Assembly

🆕  New Features

Until now, Warehouses have selected the latest artifact that matches each subscription's criteria and constraints, but this has sometimes led to undesirable behaviors:

1. If two versions of an artifact were pushed in rapid succession, a subscribed Warehouse might miss the older of the two and only create Freight using the newer one -- which is a problem if you had any interest in progressing the older of the two through your pipeline.

2. If related changes were pushed to two repositories (e.g. a new image version and its related configuration) a Warehouse subscribed to both might have found the latest artifacts and created Freight from them between the two pushes, resulting in an invalid combination, such as a new image without the new configuration that it depends on.

A few new features offer solutions to such problems:

• Warehouses now discovers many recent versions of each artifact that meet each subscription's criteria and constraints.
• Warehouses can be configured to not create Freight automatically when new artifacts are found.
• It is now possible to manually select a combination of artifacts discovered by a Warehouse to build your own Freight.
• How frequently Warehouses discover new artifacts can be configured.
• Uninterested in some piece of Freight? You can now delete it.

Assorted UI Improvements

🆕  New Features

Just the highlights:

• As with Stages and Freight, you can now open an expanded/details view of a Warehouse by clickon on it.
• Click a filter button on a Warehouse or select a Warehouse from a dropdown to apply a filter to the Freightline.
• Abort and retry verifications from the UI.
• New, lighter theme.

New Community Contributors

Last, but certainly not least, Kargo would be nothing without its community, so we'd like to acknowledge community members whose first contributions are included in this release:

• @wmiller112
• @akolacz

Thank you for helping to make Kargo better!

Full Changelog: v0.6.0...v0.7.0

v0.7.0-rc.2

chore(backport release-0.7): feat(ui): ability to delete freight (#2111)

Co-authored-by: Remington Breeze <[email protected]>
Co-authored-by: Kent Rancourt <[email protected]>

v0.7.0-rc.1

fix: refresh promotions using api server's own internal client (#2102)

Signed-off-by: Kent Rancourt <[email protected]>

v0.6.0

What's Changed

The Kargo team is thrilled to announce the release of v0.6.0, packed with stability improvements, enhancements, and new features. While the list of improvements and additions is extensive, we have highlighted some features you can look forward to exploring.

If you are looking for a more complete list, please do consult the full changelog

Notes on Upgrading

There is a single breaking change: the "well-known" kargo-secret-manager ClusterRole has been renamed to kargo-project-admin. However, this release includes a built-in upgrade reconciler to ensure a seamless upgrade process by automatically changing any project-level bindings referencing the old name to reference the new one.

⚠️ Please note that if you are upgrading from a version older than v0.5.0, you first need to upgrade to v0.5.x before upgrading to v0.6.0. This is due to breaking changes introduced in v0.5.0, for which no upgrade aid exists in this release.

Role Management

Kargo will now create two roles in every Project: kargo-admin and kargo-viewer.

The Kargo UI and CLI further allow creating and managing additional roles to provide scoped access to Kargo resources in a Project, which can be mapped to OIDC emails, subjects, and groups.

Warehouse Filters

In v0.5.0, Warehouse subscription filters using regular expressions were introduced. Making it possible to, for instance, subscribe to a monorepo, but trigger the production of new Freight only when changes to relevant paths are detected.

In this release, this feature has been further enhanced to support glob patterns (using a glob: prefix) and exact paths to files or directories. Additionally, the filters now apply to all commit selection strategies (and not just NewestFromBranch).

For more detailed information, please take a look at the Kargo documentation.

Kubernetes Events

Kargo will now emit Kubernetes Events for noteworthy changes. For example, when a new Promotion is created or the verification of Freight in a Stage succeeded. These events can also be viewed in the newly introduced events tab in the Project dashboard of the Kargo UI.

GitLab Merge Requests

In v0.3.0, support for opening a GitHub pull request was added to Git-based promotion mechanisms. With the help of @PhilippParis, this has now been expanded to support GitLab merge requests.

UI Improvements

• Project settings and AnalysisTemplate resources can now be managed through the UI.
• Variety of bug fixes and other stability improvements.

Other Notable Features

• Credentials can now include descriptions, which are displayed in the UI for informational purposes. We plan to expand this feature to more Kargo resource types in the future.
• kargo get commands now support a --no-headers flag, which will avoid printing the column headers when provided.
• kargo promote can now wait for a Promotion to finish using --wait.
• Kargo can now be configured (via the chart configuration) to sign commits with a GPG key.
• Arbitrary volumes can be mounted to the optional Dex server (via the chart configuration) to support more complex connector configurations. This can for example be useful to configure Dex's google connector to get additional Google Groups information from your users, allowing you to assign permissions to members of a Google Group.

New Contributors

Last, but certainly not least, Kargo would be nothing without its community, so we'd like to take a moment to thank community members whose first contributions to the project are included in this release:

• @blakepettersson
• @ed-boykin
• @PhilippParis
• @vavdoshka
• @zkhvan

v0.6.0-rc.2

chore: bulk backporting of recent changes from main (#1953)

Signed-off-by: Maksim Stankevic <[email protected]>
Signed-off-by: Kent Rancourt <[email protected]>
Signed-off-by: Remington Breeze <[email protected]>
Co-authored-by: Maksim Stankevic <[email protected]>
Co-authored-by: Remington Breeze <[email protected]>
Co-authored-by: Hidde Beydals <[email protected]>

v0.5.2

fix: pin to pnpm 9.0.3 anywhere it is used (#1928)

Signed-off-by: Kent Rancourt <[email protected]>

v0.6.0-rc.1

fix(promotions): only check revision match sync result if found (#1923)

Signed-off-by: Hidde Beydals <[email protected]>