Uploaded image for project: 'Distributed Tracing'
  1. Distributed Tracing
  2. TRACING-1802

OpenTelemetry Operator v1

XMLWordPrintable

    • OpenTelemetry Operator v1
    • True
    • Hide
      This epic was automatically marked as blocked because the resolution for a subtask has been set to Won't Do (or Won't Fix), indicating a functional team cannot support this epic. If you believe this occurred in error, please reach out to the functional team for help in getting this work into their queue.
      Show
      This epic was automatically marked as blocked because the resolution for a subtask has been set to Won't Do (or Won't Fix), indicating a functional team cannot support this epic. If you believe this occurred in error, please reach out to the functional team for help in getting this work into their queue.
    • False
    • Done
    • 0% To Do, 0% In Progress, 100% Done
    • Undefined

      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 epic here tracks the Operator-related tasks.

          1.
          		 Docs Tracker Sub-task Closed Undefined Unassigned
          2.
          		 QE Tracker Sub-task Closed Undefined Unassigned
          3.
          		 TE Tracker Sub-task Closed Undefined Unassigned

              Unassigned Unassigned
              jpkroehling@redhat.com Juraci Paixão Kröhling (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: