Addon opentelemetry-operator

[MdSahil-oss]

Description of your changes

Adds a new Addon opentelemetry-operator

Fixes #5774

How has this code been tested?

Checklist

I have:

• Title of the PR starts with type (e.g. [Addon] , [example] or [Doc]).
• Updated/Added any relevant documentation and examples.
• New addon should be put in experimental.
• Update addon should modify the version in metadata.yaml to generate a new version.

Verified Addon promotion rules

If this pr wants to promote an experimental addon to verified, you must check whether meet these conditions too:

• This addon must be tested by addon's e2e-test to guarantee this addon can be enabled successfully.
• This addon must have some basic but necessary information.
  • An accessible icon url and source url defined in addon's metadata.yaml.
  • A detail introduction include a basic example about how to use and what's the benefit of this addon in README.md.
  • Also provide an introduction in KubeVela documentation.
  • It's more likely to be accepted if useful examples provided in example dir.

[MdSahil-oss]

@wonderflow @wangyikewxgm This addon is done, Please review it :)

[wonderflow]

Actually this is not what this addon expected.

Assuming I'm an app developer which focus on Java. Then I'll deploy application in Java like this:

kind: Application
spec:
   components:
   - type: webservice
      properties:
          image: my-java-image

Then I want to use opentelementry addon for some data collection staff, what will I use it?

I will like to use it like:

kind: Application
spec:
   components:
   - type: webservice
      properties:
          image: my-java-image
      traits:
      - type: java-collector
         properties:
           <only-minimal-necessary-parameters-needed-here>           

After this, I hope to see the grafana dashboard working!

Don't provide all these complexity, if so, why don't the developers use the CRD operator directly?

[MdSahil-oss]

Thanks for review @wonderflow, Okay! I'll simplify this addon so that users can use it easily :)

[MdSahil-oss]

@wonderflow How about below structure:

apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
  name: otel-pod-sample-1
spec:
  components:
    - type: "k8s-objects"
      name: "otel-pod-1"
      properties:
        objects:
          - apiVersion: v1
            kind: Pod
            metadata:
              name: myapp-1
              annotations:
                sidecar.opentelemetry.io/inject: "true"
            spec:
              containers:
                - name: myapp
                  image: jaegertracing/vertx-create-span:operator-e2e-tests
                  ports:
                    - containerPort: 8080
                      protocol: TCP
      traits:
        - type: opentelemetry-collector
          name: otel-container
          properties:
            mode: sidecar
            config: |
              receivers:
                jaeger:
                  protocols:
                    thrift_compact:
              processors:

              exporters:
                logging:

              service:
                pipelines:
                  traces:
                    receivers: [jaeger]
                    processors: []
                    exporters: [logging]

[wonderflow]

Yes, this becomes better.

[MdSahil-oss]

@wonderflow Please review it again, I've added component definitions as traits & Updated the Readme.