Resource settings behave differently on otel-collector and target-allocator

[cmergenthaler]

Currently, the resource settings in OpenTelemetryCollector CRD behave differently for otel-collector and target-allocator. For the latter, default values are set if not provided which makes it impossible to i.e. unset cpu limits. On the collector, no default values are set at all, which makes it easy to customize to the pods' needs.

The following example will result in different setups for otel-collector and target-allocator. TA will have a default cpu limit of 200m, collector will have an unset cpu limit.

apiVersion: opentelemetry.io/v1alpha1
kind: OpenTelemetryCollector
metadata:
  name: otel
spec:
  mode: deployment
  resources:
    requests:
      cpu: 150m
      memory: 200Mi
    limits:
      memory: 500Mi
  targetAllocator:
    enabled: true
    resources:
      requests:
        cpu: 150m
        memory: 200Mi
      limits:
        memory: 500Mi

[yuriolisa]

/assign

[Toaddyan]

/assign