open-telemetry/opentelemetry-operator v0.138.0

Release v0.138.0

on GitHub

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

• OpenTelemetry Collector - v0.138.0

• OpenTelemetry Contrib - v0.138.0

• Java auto-instrumentation - v1.33.6

• .NET auto-instrumentation - v1.2.0

• Node.JS - v0.64.1

• Python - v0.59b0

• Go - v0.22.1

• ApacheHTTPD - 1.0.4

• Nginx - 1.0.4

  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