chore: Upgraded otel core to 0.108.0 #1678
Merged
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
repo was changed from
github.com/open-telemetry/opentelemetry-collector
togithub.com/open-telemetry/opentelemetry-collector-releases
for curling the binaryremove
@$(MAKE) ensure-correct-builder-version
in Makefile because the check will show(devel)
isn't the same as0.108.0
to unblock failed buildversion: (devel)
output showing up from upstream v107+2024-09-30T12:15:44.182-0700 INFO internal/command.go:127 OpenTelemetry Collector Builder {"version": "(devel)"}
Deprecated functions:
NewCommandMustSetProvider
was deprecated in v107 -> useNewCommand
expandconverter
was deprecated in v107: https://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.107.0 -> useenvprovider
NewInformer
inclient-go v0.31.1
deprecated inrawk8seventreceiver
: https://pkg.go.dev/k8s.io/client-go/tools/cache#NewInformer -> useInformerOptions
just a heads up for the future, in upstream components
googlecloudmonitoringreceiver
was added upstream BUT its in development state, we start adding to.otelcolbuilder
andREADME
once in alpha+Testing