Understanding an object's provenance - should we track parents?

[brandonjbjelland]

I wonder if it'd be valuable to have a common .status.parent field particularly for Dataset and Model. This is coming back to a need to understand a model's (and dataset's) lineage since we don't have a concept of pipelines (with a history) which would otherwise tell the story.

[nstogner]

The scenario where one object created another object is typically tracked with owner references in kubernetes: https://kubernetes.io/docs/concepts/overview/working-with-objects/owners-dependents/

[nstogner]

Once we start enforcing immutability of .spec fields we will be able to trust the lineage specified there (i.e. .spec.trainingDataset in a Model).