To integrate with  korrel8r we need to:

1. Create a korrel8r domain for tracing that can to the tracing store and query for traces. This is  a fixed-size task to make korrel8r "trace aware".  May need some "domain expert" help from tracing team to understand how traces are represented and queried. 
2. Create rules that associate traces with objects in other domains. The rule set is open, so we want to identify the most compelling cases for the tech preview and we can build up the rule set in future. A "use case" is a question like:
   • I'm looking at this object (alert/deployment/log record/pod/netevent...) what traces are related to it?
   • I'm looking at a set of traces, what objects (alerts etc.) are related to them?

Korrel8r chains relationships so e.g. if you can relate traces to/from Pods, then you can also relate them to/from anything a pod is related to. The trace part of the rule set only needs to express direct relationships, korrel8r will add those rules in its total rule set to find indirect relationships.

Upstream issue: https://github.com/korrel8r/korrel8r/issues/6