Skip to content

Stop honoring deprecated telemetry.metrics.address#5231

Draft
ozzywalsh wants to merge 1 commit into
open-telemetry:mainfrom
ozzywalsh:fix/remove-stale-metrics-address
Draft

Stop honoring deprecated telemetry.metrics.address#5231
ozzywalsh wants to merge 1 commit into
open-telemetry:mainfrom
ozzywalsh:fix/remove-stale-metrics-address

Conversation

@ozzywalsh

@ozzywalsh ozzywalsh commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Stop parsing telemetry.metrics.address for the monitoring service; log a deprecation warning instead
  • The v0.122.0 upgrade function already migrates addressreaders automatically, so this field should no longer be present in practice
  • Inject default telemetry readers when only address is set (since the collector ignores it)

The collector fully removed support for the address field; it now uses
readers exclusively. The operator was still acting on address in
MetricsEndpoint() and ServiceApplyDefaults(), causing the Kubernetes
Service port to diverge from the actual collector metrics endpoint.

Now address is ignored with a deprecation warning, and the operator
always derives the metrics endpoint from readers or defaults. The
upgrade system (v0_122_0) already migrates address to readers for
existing CRs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant