Events are emitted when choreography edits resources or notices a change in their output or healthy state. Don’t treat events like logs, however they can offer valuable insight into what’s happening in a supply chain over time. For example, very high occurrences of events in a short period of time might be a sign of resources thrashing.
Events are published on Workload, Deliverable, and Runnable resources. You can view them manually using:
kubectl describe workload.carto.run <workload-name> -n <workload-ns> kubectl describe runnable.carto.run <runnable-name> -n <runnable-ns> kubectl describe deliverable.carto.run <deliverable-name> -n <deliverable-ns>
The following sections define the different events.
This event is emitted every time choreography creates or updates a resource. The created or updated resource is referenced in the event message.
Created object [gitrepositories.source.toolkit.fluxcd.io/my-project] Updated object [apps.kappctrl.k14s.io/my-project-app]
This event is emitted every time choreography deletes a resource. This currently only occurs when Runnable resources expire. The deleted object is referenced in the event message.
Deleted object [task.tekton.dev/my-project-a737bdf]
This event is emitted every time choreography recognizes a new output from a resource.
[source-provider] found a new output in [imagerepositories.source.apps.tanzu.vmware.com/app]
This event is emitted every time choreography recognizes that the healthy status of a resource has changed.
[image-provider] found healthy status in [images.kpack.io/app] changed to [True] [source-provider] found healthy status in [[gitrepositories.source.toolkit.fluxcd.io/my-project]] changed to [False]