opentelemetry-operator icon indicating copy to clipboard operation
opentelemetry-operator copied to clipboard

Collector ConfigMap doesn't get updated when adding a field with the same value as another contiguous field

Open fabiobaiao opened this issue 4 months ago • 1 comments

Component(s)

collector

What happened?

Description

A Collector's ConfigMap doesn't get updated when adding the sending_queue.batch.min_size of the exporter helper on the otlp exporter with the same value as an already existing sending_queue.batch.max_size.

Not sure if it is something specific to this configuration or if it's something more generic.

If a different value is used, the ConfigMap is correctly updated. Moreover if they are added simultaneously, the ConfigMap is also updated correctly, but if one of them is removed afterwards it doesn't get updated.

Steps to Reproduce

Create a Collector with the following config:

exporters:
  otlp:
    sending_queue:
      batch:
        flush_timeout: 200ms
        max_size: 4194304

After applying it add the following field:

exporters:
  otlp:
    sending_queue:
      batch:
        min_size: 4194304

Expected Result

The ConfigMap should be updated accordingly:

exporters:
  otlp:
    sending_queue:
      batch:
        flush_timeout: 200ms
        max_size: 4194304
        min_size: 4194304

Actual Result

The ConfigMap isn't updated:

exporters:
  otlp:
    sending_queue:
      batch:
        flush_timeout: 200ms
        max_size: 4194304

Kubernetes Version

1.32.5

Operator version

0.129.1

Collector version

0.130.0

Environment information

No response

Log output


Additional context

No response

fabiobaiao avatar Jul 29 '25 10:07 fabiobaiao

I see a similar problem with the "processors.memory_limiter" field, though in my case it has to do with the operator leaving previous fields in place that should no longer be present.

seh avatar Oct 03 '25 13:10 seh