Skip to content

v0.7.0
Compare
Choose a tag to compare
@krancour krancour released this 07 Jun 20:11
· 7 commits to release-0.7 since this release
v0.7.0
607230d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

💥  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:

Thank you for helping to make Kargo better!

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

Contributors

akolacz and wmiller112
Assets 10
Loading