Artifact Tracing with Correlation Rules

[waciumawanjohi]

Readable

• [ ] Linked to a relevant issue. Eg: Fixes #123 or Updates #123
• Removed non-atomic or wip commits
• [ ] Filled in the Release Note section above
• [ ] Modified the docs to match changes

[waciumawanjohi]

Following feedback, the RFC no longer includes caching of any values.

[squeedee]

Love it!

[idoru]

LGTM!

[scothis]

What resources choreographed by Cartographer follow this pattern today? Without knowing that we are picking up support for common patterns that exist in the wild, this proposal has an element of "if you build it, they will come" vibes.

[waciumawanjohi]

What resources choreographed by Cartographer follow this pattern today? Without knowing that we are picking up support for common patterns that exist in the wild, this proposal has an element of "if you build it, they will come" vibes.

The only resource I know of that would fit would be Tekton, where a Tekton task status includes the spec definition that led to the output.

I agree that this and Artifact Tracing with Generation Output Correlation are Cartographer encouraging the k8s resources in our domain to adopt one of these patterns. If those other resources never do, tracing will always rely on Artifact Tracing with Health Rules, which is sub-optimal.