Broken imports of go.opentelemetry.io/otel/sdk for 1.21.0

[JeromeJu]

When we are trying to bump go.opentelemetry.io/otel/sdk from 1.19.0 to 1.21.0, the build test failure indicates the tracerProvider @HEAD has not implemented the interface from the upstream.

pkg/reconciler/taskrun/controller.go:92:30: cannot use tracerProvider (variable of type *tracing.tracerProvider) as type "go.opentelemetry.io/otel/trace".TracerProvider in struct literal:
	*tracing.tracerProvider does not implement "go.opentelemetry.io/otel/trace".TracerProvider (missing tracerProvider method)

When looking into this, there seems to be 2 issues that need verification:

• The tracerProvider interface has changed in this version upgrade with an embeddedTracerProvider: https://github.com/open-telemetry/opentelemetry-go/blob/d37d851bbce65577ab340849ec6c540fdc6e3096/trace/embedded/embedded.go#L36
• trace.NewNoopTracerProvider() is deprecated and the up-to-date func should have the interface implemented.

Originally posted by @JeromeJu in #7387 (comment)

[JeromeJu]

cc @kmjayadeep as you might have more inputs on the implementation of tracerProvider.

[kmjayadeep]

I'm working on updating to otel 1.21. It also deprecated jaeger exporter in favor of otel exporter, which makes the update not so-straightforward.
You can find the WIP PR here

Is this blocking anyone currently?

[JeromeJu]

I'm working on updating to otel 1.21. It also deprecated jaeger exporter in favor of otel exporter, which makes the update not so-straightforward. You can find the WIP PR here

Thanks for this! I think this PR also works fine for the bump, just failed the go coverage test IIUC.

Is this blocking anyone currently?

I don't think this is a blocker at the moment.

[vdemeester]

@kmjayadeep the bump to containerd "seems" blocked on this.

[vdemeester]

A lot of dependabot PRs are blocked on this. For some reason, dependabot tries to update it with other dependencies, making them all fail (instead of just updating the ones).

[kmjayadeep]

@vdemeester I will check my WIP PR once again and raise upstream in the next couple of days

[JeromeJu]

I can reopen this #7465 if it looks good. @vdemeester @kmjayadeep

[kmjayadeep]

The proper solution is to migrate jaeger to otel exporter and upgrade to 1.21. I have raised #7547 for this.

@JeromeJu In your PR, jaeger exporter is from otel 1.17 and SDK is 1.21. I'm not sure if there will be any compatibility issues with that. But if it works without issues, I would suggest to go ahead with it and unblock others. I can rebase afterwards on my PR. 7547 will take longer to review and test anyway.