Skip to content

fix(deps): Build the collector on OpenTelemetry Go v1.47 - #278

Merged
ecv merged 1 commit into
mainfrom
fix/otelcol-v0.165-otel-v1.47
Nov 17, 2026
Merged

ecv merged 1 commit into
mainfrom
fix/otelcol-v0.165-otel-v1.47

Conversation

@ecv

@ecv ecv commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

Summary

The OpenTelemetry Go v1.47.0 security fix for GHSA-q7gw-24fr-5p69 cannot merge, because the collector image stops building with it.

The fix pulls in the stable OpenTelemetry log API, and the collector at v0.157.0 still bundles a logging bridge written against the older one.

This moves the collector build and every component to v0.165.0, which is built on OpenTelemetry Go v1.47.0, and carries the v1.47.0 bumps from #274 and #275 in the same change.

Once it merges, #274, #275 and #276 have nothing left to add.

Test plan

  • The collector image builds and publishes for both architectures
  • Module builds and tests pass, with the operator controller suite judged against main

Fixes #277

The OpenTelemetry Go v1.47.0 security fix (GHSA-q7gw-24fr-5p69) cannot
land on its own: it pulls in the stable otel/log v1.47.0, and collector
v0.157.0's otelzap bridge no longer compiles against it, so the otelcol
image build fails. Moving the collector to v0.165.0, which is built on
OTel v1.47.0, lets the security bump and the image build land together.

Key features/changes:
- Move every builder-config component and the OCB builder to v0.165.0;
  k8sattributesprocessor is now on its stable line, v1.4.0, which is the
  same contrib commit as v0.165.0
- Move natsreceiver, natsexporter and unbatchprocessor to collector
  v1.71.0 / v0.165.0 so OCB resolves one consistent set
- Bump otel, otel/sdk, otel/trace and otel/metric to v1.47.0 and testify
  to v1.12.1 in operator, queryapi and clickhouse-migrate, as #274 and
  #275 propose

Fixes #277
@ecv ecv added dependencies Pull requests that update a dependency file go Pull requests that update go code security labels Nov 16, 2026
@ecv
ecv marked this pull request as ready for review November 16, 2026 21:56
@ecv
ecv requested a review from a team as a code owner November 16, 2026 21:56
@ecv
ecv requested a review from kevwilliams November 16, 2026 21:56
@ecv
ecv enabled auto-merge November 16, 2026 21:56
@ecv

ecv commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor Author

Two reviews agree, and CI is green on 2bfe44b, including the otelcol image for both architectures and the operator suite.

The correctness review built the collector at v0.165.0 and ran otelcol validate against the gateway, node-agent and sink collector configs. All three pass, and a bogus key fails as a control. Every module the advisory covers resolves to otel, sdk, sdk/log and trace at v1.47.0 or later. No breaking change between v0.158 and v0.165 touches a setting those configs use. k8sattributesprocessor v1.4.0 and contrib v0.165.0 point at the same commit, f56f9a38.

The blast-radius review found that merging rolls the new bundle to the staging o11y sink and the staging edge labs within about a minute. Production stays on the v0.6.10 pin until a release and an infra pin PR.

After merge, #274, #275, #276 and the abandoned #250 can close. #273 (x/crypto) still needs to land and will want a rebase.

@andrewb3000 andrewb3000 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Non-blocking

  • config/collectors/gateway-collector.yaml:86: No CI job runs the gateway, node-agent and sink configs against the new binary, so a setting removed between v0.157 and v0.165 would only show as a crashloop after release. Run otelcol validate on all three configs, or watch staging, before the next release tag.

Checked

  • otelcol/builder-config.yaml:28: k8sattributesprocessor is pinned at v1.4.0 while the other contrib components use v0.165.0. The version does exist: publish.yaml builds the otelcol image on PRs for amd64 and arm64, and that build passed.
  • operator/go.mod:80: In operator and queryapi, otel/exporters/otlp/otlptrace* stays at v1.45.0 while the otel core moves to v1.47.0. Both modules still build and their tests pass, so this is fine, but Renovate will likely open follow-up PRs for those exporters.

@ecv
ecv merged commit a228d2a into main Nov 17, 2026
31 of 32 checks passed
@ecv
ecv deleted the fix/otelcol-v0.165-otel-v1.47 branch November 17, 2026 21:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file go Pull requests that update go code security

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Collector image fails to build once components move to OpenTelemetry v1.47

2 participants