[processor/k8sattributes] Add support for profiles signal

[mx-psi]

Component(s)

processor/k8sattributes

Describe the issue you're reporting

This processor would be useful for testing and validation of the experimental profiling signal, and to replace some functionality available in the eBPF Agent.

As inspiration for how to add support this PR can be used: open-telemetry/opentelemetry-collector/pull/11071 (there is no processor with support as of the writing of this issue)

Example of configuration using profiles (needs service.profilesSupport feature gate to be enabled):

receivers:
  otlp:
    protocols:
      grpc:
exporters:
  otlp:
    endpoint: ${OTLP_ENDPOINT}
service:
  pipelines:
    profiles:
      receivers: [otlp]
      exporters: [otlp]

[github-actions]

Pinging code owners:

• processor/k8sattributes: @dmitryax @fatsheep9146 @TylerHelmuth

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[haoqixu]

The package go.opentelemetry.io/collector/processor/processorhelper lacks profile support. Should we extend the *helper package or implement the helper struct/functions in a separate package? The same issue exists for receiverhelper and exporterhelper.

[mx-psi]

processorhelper only handles telemetry. Since we are going to rework that API, I would prefer to leave telemetry out of the picture for now (same thing we did for receivers, see open-telemetry/opentelemetry-collector#11071 (comment)). For exporters, we have a dedicated module for profiles

[haoqixu]

processorhelper only handles telemetry. Since we are going to rework that API, I would prefer to leave telemetry out of the picture for now (same thing we did for receivers, see open-telemetry/opentelemetry-collector#11071 (comment)). For exporters, we have a dedicated module for profiles

Thank you for the information. I will submit a PR soon.