Scott Andrews

`ko` can build multi-arch images, but it requires the base image to support each of the desired architectures. The output of ko will be an image manifest, so all downstream...

> Will need an arm ytt binary. https://github.com/vmware-tanzu/carvel-ytt/releases/download/v0.41.1/ytt-linux-arm64

Have we implemented these ideas to see how they perform in a cluster? There are enough moving parts that to prove correct behavior in every situation will be difficult (the...

If we step back and look at the larger picture of artifact tracing in the context of the Blueprints API, what would an artifact tracing native API look like?

"status" is a bit overloaded. I don't think a stamped resource should be able to have its full/partial `.status` reflected blindly on the workload, but I do like the idea...

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...

> The problem that we are trying to address is make it easy for the user to be able to identify the artifact graph that gets produced by a supply...

> Should workload artifacts be wiped out when spec changes? If yes, can we fast forward through the supply chain matching known inputs to outputs and rebuild the artifact tree...

Borrowing from the intent behind this RFC and 20, I'd like to propose an alternate status shape for Workloads. Not all of the fields are expected to be populatable immediately,...

@cirocosta inputs/outputs were not intended to be a historical record of how a value changed over time, but to capture the "current" output/input for a resource. The definition of current...