New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vendor: upgrade OpenTelemetry libraries to v1.19.0 / v0.45.0 (carry) #4356
Conversation
Core OTel libs are now at v1.19.0, while contrib is at v0.45.0. The protocol has also reached 1.0.0. Note that Jaeger exporter is frozen at v1.17.0, which is the last version it was supported by OpenTelemetry. BuildKit should likely begin the process of deprecating it as well, since OTLP is now the recommended solution (by Jaeger themselves), but that is not handled here. Co-authored-by: CrazyMax <crazy-max@users.noreply.github.com> Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
fixes security issue (CVE-2023-44487) Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
@milas validate-docs does not look happy when running
Added extra commit with smoke tests for the binaries and it seems to complain about otel updates: https://github.com/moby/buildkit/actions/runs/6586246066/job/17894247170#step:5:480
Same for any integration tests: https://github.com/moby/buildkit/actions/runs/6586246066/job/17894326770?pr=4356#step:8:12727 |
Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
Schema should be 1.19.0 but semconv is set to 1.17.0: https://github.com/open-telemetry/opentelemetry-go-contrib/blob/instrumentation%2Fgoogle.golang.org%2Fgrpc%2Fotelgrpc%2Fv0.45.0/instrumentation/google.golang.org/grpc/otelgrpc/internal/parse.go#L21. Release notes is lying: https://github.com/open-telemetry/opentelemetry-go-contrib/releases/tag/v1.20.0 |
Ok now found out |
related to containerd/containerd#9256 (comment)