Given the distributed tracing landscape is moving towards OpenTelemetry, we should embrace it as this give our customer benefits of security, expansibility, modularity, and multitenancy.

We should assist the OpenTelemetry community by providing engineering resources for completing a v1 before the end of this year, and by providing a Kubernetes Operator that can also be used in OpenShift.

The goal here is to provide a tech-preview of the operator by 2021-08-01, without waiting for the v1 of the collector. Once OpenTelemetry Collector reaches GA, we should release the v1 of the operator, by marking the CRD as `v1` as well. Both components are likely having only the tracing aspect supported in a first moment.

How does this align with the strategy?

• We can use OpenTelemetry Collector as a gateway to other features, such as multitenancy and security. 
• OpenTelemetry give us a modular capability and leverage our potential partners 

This requires effort only from our team.

This epic here tracks only the collector-related tasks.