Skip to content

Conversation

@chaplain-grimaldus
Copy link
Contributor

@chaplain-grimaldus chaplain-grimaldus bot commented Sep 12, 2025

This PR contains the following updates:

Package Update Change
otel-operator-source minor v0.132.0 -> v0.139.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

open-telemetry/opentelemetry-operator (otel-operator-source)

v0.139.0

Compare Source

0.139.0

💡 Enhancements 💡
  • operator: Promote the operator.sidecarcontainers.native feature flag to Stable. (#​4451)
    By default, the operator will continue to use native sidecars on Kubernetes versions
    newer than 1.29. This behaviour cannot be disabled.
    The operator flag will be removed with the release of version 0.140.0.

  • collector: Promote the operator.collector.default.config feature gate to Stable (#​4453)

Components

v0.138.0

Compare Source

0.138.0

💡 Enhancements 💡
  • collector: Migrate simple OpenTelemetryCollector validations from the webhook to CRD annotations so Kubernetes enforces them server-side. ()
🛑 Breaking changes 🛑
  • target allocator: Remove the operator.collector.targetallocatorcr feature flag (#​2422)
    This behavior has been enabled by default since version 0.127.0.
🚩 Deprecations 🚩
  • auto-instrumentation: Deprecate VolumeSizeLimit in the Instrumentation CRD (#​3382)
    • The volumeSizeLimit field is deprecated.
    • Use spec.<lang>.volume.size instead of spec.<lang>.volumeSizeLimit.
    • The validating webhook emits a warning when volumeSizeLimit is used.
🧰 Bug fixes 🧰
  • target allocator: Add missing TA ownership watches to cert-manager Certificate and Issuer (#​4368)
  • collector: Set the log level to 4 when default pdb is created. ()
  • collector: Fix autoscaler not scaling above minReplicas; replicas now respect the scale subresource and never fall below autoscaler.minReplicas. (#​4400) Also rename helper GetInitialReplicas to GetDesiredReplicas to reflect reconcile-time behavior.
Components
💡 Enhancements 💡
  • collector: Add logs when the Operator finds an issue during the unmarshall process for spec.service.telemetry section. (#​4111)
  • collector: Add spec.dnsPolicy field to the OpenTelemetryCollector to allow users to specify the DNS policy for the collector pods. (#​4265)
  • github action: Add link checking workflow to validate documentation (#​3425)
    • Added ci-markdown-link.yml workflow using linkspector to check for broken links in markdown files
    • Added .linkspector.yml configuration file
  • collector: add startup probe to the collector CRD (#​4347)
  • collector: Validate collector ports from the config to ensure they are within the valid range (1-65535). (#​4399)
    • This change adds validation for collector ports specified in the configuration file.
    • Ports must be within the range of 1 to 65535; otherwise, an error will be raised during CR creation.
    • This helps prevent misconfigurations that could lead to runtime errors.
🧰 Bug fixes 🧰
  • collector: Respect telemetry metrics readers when deriving the internal metrics endpoint. (#​4049, #​4233)

    • Fixes monitoring Service and container port mismatches when .spec.config.service.telemetry.metrics.readers[].pull.exporter.prometheus.port is set.
    • Defaults remain 0.0.0.0:8888 when neither address nor a Prometheus reader is configured.
  • target allocator, opamp: Fix version not being updated after version upgrade. (#​4378)

  • target-allocator: Fixed potential duplicate scrape targets caused by Prometheus relabeling. (#​3617)

  • auto-instrumentation: Fix nginxCloneScriptTemplate for old shells (#​3651)

Components

v0.137.0

Compare Source

0.137.0

🛑 Breaking changes 🛑
  • target allocator: Promote the operator.collector.targetallocatorcr feature flag to Stable (#​2422)
    The flag can no longer be disabled. It will be completely removed in 0.138.0.
💡 Enhancements 💡
  • collector: Add logs when the Operator finds an issue during the unmarshall process for spec.service.telemetry section. (#​4111)
  • collector: Add spec.dnsPolicy field to the OpenTelemetryCollector to allow users to specify the DNS policy for the collector pods. (#​4265)
  • github action: Add link checking workflow to validate documentation (#​3425)
    • Added ci-markdown-link.yml workflow using linkspector to check for broken links in markdown files
    • Added .linkspector.yml configuration file
  • collector: add startup probe to the collector CRD (#​4347)
  • collector: Validate collector ports from the config to ensure they are within the valid range (1-65535). (#​4399)
    • This change adds validation for collector ports specified in the configuration file.
    • Ports must be within the range of 1 to 65535; otherwise, an error will be raised during CR creation.
    • This helps prevent misconfigurations that could lead to runtime errors.
🧰 Bug fixes 🧰
  • collector: Respect telemetry metrics readers when deriving the internal metrics endpoint. (#​4049, #​4233)

    • Fixes monitoring Service and container port mismatches when .spec.config.service.telemetry.metrics.readers[].pull.exporter.prometheus.port is set.
    • Defaults remain 0.0.0.0:8888 when neither address nor a Prometheus reader is configured.
  • target allocator, opamp: Fix version not being updated after version upgrade. (#​4378)

  • target-allocator: Fixed potential duplicate scrape targets caused by Prometheus relabeling. (#​3617)

  • auto-instrumentation: Fix nginxCloneScriptTemplate for old shells (#​3651)

Components

v0.136.0

Compare Source

0.136.0

🧰 Bug fixes 🧰
  • target-allocator: Fixes the incorrect k8s version for the traffic distribution feature. (#​4394)
  • collector: Fix statefulset serviceName field change handling. (#​4371)
    The Operator 0.129.1 introduced a new feature which allows setting the serviceName of the collector statefulset (#​4041).
    This feature introduced two issues:
    1. upgrade failure because the default stateful serviceName changed
    2. the statefulset serviceName field is mutable, therefore a change of the collector serviceName field is not applied
Components

v0.135.0

Compare Source

0.135.0

💡 Enhancements 💡
  • collector, target allocator: Add TrafficDistribution support for OpenTelemetryCollector and TargetAllocator Services (#​4285)
    The TrafficDistribution field is now available in OpenTelemetryCollector and TargetAllocator.
    This field allows setting the traffic distribution policy for Kubernetes Services.
Components

v0.134.0

Compare Source

0.134.0

💡 Enhancements 💡
  • target allocator: Add CollectorTargetReloadInterval option to configure the interval at which the Prometheus receiver reloads targets from the target allocator (#​4095)
🧰 Bug fixes 🧰
  • collector: Always return a valid OpenTelemetryCollector configuration during v1beta1 conversion. (#​4288)
Components

0.133.0

⚠️ Skip Release ⚠️
  • operator: Skipped OpenTelemetry Operator release due to an issue on the collectors protobuf parsing that caused HTTP 400 errors for metric submissions. In case of expecitly using the collector v0.133.0 this behavior can be by passed by disabling the collector feature gate pdata.useCustomProtoEncoding.
    For more details see: (opentelemetry-collector#13727)[open-telemetry/opentelemetry-collector#13727]
apiVersion: opentelemetry.io/v1beta1
kind: OpenTelemetryCollector
metadata:
  name: my-collector
spec:
  image: otel/opentelemetry-collector:0.133.0
  args:
    - --feature-gates=-pdata.useCustomProtoEncoding

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@chaplain-grimaldus chaplain-grimaldus bot force-pushed the renovate/otel-operator-source-0.x branch from b57de18 to e79f9d8 Compare September 16, 2025 17:04
@chaplain-grimaldus chaplain-grimaldus bot changed the title feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.134.0 ) feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.135.0 ) Sep 16, 2025
@chaplain-grimaldus chaplain-grimaldus bot force-pushed the renovate/otel-operator-source-0.x branch from e79f9d8 to d5e0271 Compare September 30, 2025 08:05
@chaplain-grimaldus chaplain-grimaldus bot changed the title feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.135.0 ) feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.136.0 ) Sep 30, 2025
@chaplain-grimaldus chaplain-grimaldus bot force-pushed the renovate/otel-operator-source-0.x branch from d5e0271 to 52fcd85 Compare October 20, 2025 14:04
@chaplain-grimaldus chaplain-grimaldus bot changed the title feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.136.0 ) feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.137.0 ) Oct 20, 2025
@chaplain-grimaldus chaplain-grimaldus bot force-pushed the renovate/otel-operator-source-0.x branch from 52fcd85 to bbdc8a1 Compare October 31, 2025 19:05
@chaplain-grimaldus chaplain-grimaldus bot changed the title feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.137.0 ) feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.138.0 ) Oct 31, 2025
@chaplain-grimaldus chaplain-grimaldus bot force-pushed the renovate/otel-operator-source-0.x branch from bbdc8a1 to 4246703 Compare November 7, 2025 16:04
@chaplain-grimaldus chaplain-grimaldus bot changed the title feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.138.0 ) feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.139.0 ) Nov 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant