Skip to main content

Kargo Event Reference

This document contains a complete reference of all Kargo events, including their types and descriptions.

info

These events are always emitted by Kargo to the Kubernetes event log with the keys encoded in the annotations of the event. However, they are primarily consumed by the Pro version of Kargo (such as the Notification feature)

Event Fields

Many Kargo events share common fields. The following sections describe these common fields, which are referenced in individual event definitions. Each field is given as it appears in the event payload (serialized as JSON) and, if optional, notes whether the type is a pointer when used in expr-lang expressions.

In each event definition in Event Types, the included fields are listed under "Payload Includes" with references to the relevant sections. All of the fields described in those events are found at the top level of the event payload unless otherwise noted.

Common Event Fields

These fields are included in all Kargo events:

Field NameTypeDescriptionOptional
projectStringThe project name the event originated from.No
actorStringThe user or system that triggered the event.Yes (is pointer)
messageStringA human-readable message describing the event.No (may be empty)
idStringA unique identifier for the event.No

Freight Fields

Freight payloads describe the collection of artifacts under evaluation or promotion.

Field NameTypeDescriptionOptional
nameStringName of the freight object.No
stageNameStringStage associated with the freight when the event fired.No
createTimeString (RFC3339)Creation timestamp of the freight object.No
aliasStringHuman-friendly alias assigned to the freight.Yes (is pointer)
commitsArray<GitCommit>Git commits that compose the freight (see GitCommit fields).Yes
imagesArray<Image>Container images included in the freight (see Image fields).Yes
chartsArray<Chart>Helm charts included in the freight (see Chart fields).Yes

GitCommit Fields

Field NameTypeDescriptionOptional
repoURLStringURL of the Git repository.Yes
idStringCommit SHA in the referenced repository.Yes
branchStringBranch where the commit was discovered.Yes
tagStringTag that resolved to the commit.Yes
messageStringCommit message subject line.Yes
authorStringAuthor of the commit.Yes
committerStringCommitter recorded for the commit.Yes

Image Fields

Field NameTypeDescriptionOptional
repoURLStringRepository that hosts the container image.Yes
tagStringMutable tag identifying a version of the image.Yes
digestStringImmutable digest identifying the image content.Yes
annotationsMap<String,String>Arbitrary metadata associated with the image.Yes

Chart Fields

Field NameTypeDescriptionOptional
repoURLStringHelm chart repository URL.Yes
nameStringChart name within the repository (empty for OCI-style references).Yes
versionStringSpecific chart version selected for inclusion in the freight payload.Yes

Freight Verification Fields

Freight verification metadata accompanies events emitted while verifying freight.

Field NameTypeDescriptionOptional
verificationStartTimeString (RFC3339)Timestamp when the verification run began.Yes (is pointer)
verificationFinishTimeString (RFC3339)Timestamp when the verification run finished.Yes (is pointer)
analysisRunNameStringName of the Argo Rollouts AnalysisRun created for the verification, if present.Yes (is pointer)
analysisTriggeredByPromotionStringName of the promotion that triggered the verification analysis run, if present.Yes (is pointer)

Promotion Fields

Promotion payloads describe a promotion resource and the freight it targets.

Field NameTypeDescriptionOptional
freightObject (Freight fields)Snapshot of the freight referenced by the promotion.Yes (is pointer)
nameStringName of the promotion resource.No
stageNameStringStage targeted by the promotion.No
createTimeString (RFC3339)Creation timestamp of the promotion resource.No
applicationsArray<NamespacedName>Argo CD applications resolved for the promotion step.Yes

Applications Entry Fields

Each promotion applications entry is a Kubernetes NamespacedName tuple.

Field NameTypeDescriptionOptional
namespaceStringNamespace that contains the Argo CD app.No
nameStringName of the Argo CD application.No

Event Types

The complete list of built-in Kargo event types is provided below:

  • PromotionCreated
  • PromotionSucceeded
  • PromotionFailed
  • PromotionErrored
  • PromotionAborted
  • FreightApproved
  • FreightVerificationSucceeded
  • FreightVerificationFailed
  • FreightVerificationErrored
  • FreightVerificationAborted
  • FreightVerificationInconclusive
  • FreightVerificationUnknown

Below are the detailed definitions for each event type.

PromotionCreated

This event is emitted when a promotion resource is created.

Payload Includes

PromotionSucceeded

This event is emitted when a promotion completes successfully. The payload matches PromotionCreated with one additional field.

Payload Includes

Unique to this event:

Field NameTypeDescriptionOptional
verificationPendingBooleanIndicates whether post-promotion freight verification is still outstanding.Yes (is pointer)

PromotionFailed

This event is emitted when a promotion fails, typically because a step or verification did not succeed.

Payload Includes

PromotionErrored

This event is emitted when a promotion encounters an unexpected error.

Payload Includes

PromotionAborted

This event is emitted when a promotion run is aborted before completion.

Payload Includes

FreightApproved

This event is emitted when freight is manually approved for a stage.

Payload Includes

FreightVerificationSucceeded

This event is emitted when freight verification completes successfully.

Payload Includes

FreightVerificationFailed

This event is emitted when freight verification completes with a failure.

Payload Includes

FreightVerificationErrored

This event is emitted when freight verification encounters an unexpected error.

Payload Includes

FreightVerificationAborted

This event is emitted when freight verification is aborted before completion.

Payload Includes

FreightVerificationInconclusive

This event is emitted when freight verification finishes with an inconclusive result.

Payload Includes

FreightVerificationUnknown

This event is emitted when freight verification ends in an unknown state.

Payload Includes