Resolve OTel serviceVersion at runtime instead of persisting it #3789
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
serviceVersionresolution from config creation time to runtime inNewProvider(), so it always reflects the running binary versionDefaultConfig(),MaybeMakeConfig(),createTelemetryConfig(), and operator'sNormalizeTelemetryConfig()serviceVersion(e.g., from the K8s operator CRD) are still honoredthv exportwould also capture the stale versionCloses #2296
Test plan
go test ./pkg/telemetry/...passesgo test ./cmd/thv-operator/pkg/spectoconfig/...passesgo test ./cmd/thv-operator/pkg/vmcpconfig/...passes🤖 Generated with Claude Code