Subscribing to Chainguard CloudEvents

Thu, 24 Apr 2025 15:22:20 +0100

Chainguard implements CloudEvents, a specification for a standard format for events data. This means developers can use events (generated based on interactions with Chainguard resources) to initiate processes and thus automate certain actions. For example, you could set up infrastructure to listen for push events to an organization’s private registry and mirror any new Chainguard Containers in the registry to a third-party repository.

This article includes an example of how to use chainctl to create an event subscription. It also includes details on how to validate events from Chainguard and highlights some potential use cases for them. This article is primarily focused on Registry push and pull events. Push events occur when an image in your entitlement is added or updated. Pull events occur when an image is pulled from your Chainguard repository. Be aware, though, that there are also events related to IAM, such as user creation and adding identity providers.

Mirror new Containers to Google Artifact Registry with Chainguard CloudEvents

Fri, 24 May 2024 15:22:20 +0100

Certain interactions with Chainguard resources will emit CloudEvents that you or an application can subscribe to. This allows you to do things like receive alerts when a user downloads one or more of your organization’s private container images or when a new image gets added to your organization’s registry.

This tutorial is meant to serve as a companion to the Image Copy GCP example application. It will guide you through setting up infrastructure to listen for push events on an organization’s private registry and mirror any new Chainguard Containers in the registry to a repository in a GCP Artifact Registry repository.

CloudEvents on

Subscribing to Chainguard CloudEvents

Mirror new Containers to Google Artifact Registry with Chainguard CloudEvents