Possible outdated versions.txt

[szilagyif]

Component(s)

No response

Describe the issue you're reporting

Is it possible that the autoinstrumentation-java version in the versions.txt file is not up to date? It says it should match the version in autoinstrumentation/java/version.txt, but it was not changed since v.0.116.0.

[iblancasa]

opentelemetry-operator/RELEASE.md

Line 12 in 5498cb2

> DO NOT BUMP JAVA PAST `1.X.X` AND DO NOT BUMP .NET PAST `1.2.0`. Upgrades past these versions will introduce breaking HTTP semantic convention changes.

[szilagyif]

Could someone confirm that currently there is no way to use java instrumentation 2.11.0 or higher at all? It contains an enchancement what we are waiting for.

[iblancasa]

@szilagyif the problem is that it contains some breaking changes from the semantic conventions point of view. @open-telemetry/operator-maintainers do you remember what do we agree to wait before doing the version bumping?

[swiatekm]

Could someone confirm that currently there is no way to use java instrumentation 2.11.0 or higher at all? It contains an enchancement what we are waiting for.

You can use it by manually setting it in your Instrumentation CR. You can also change the default at the operator level via the --auto-instrumentation-java-image command-line flag.

versions.txt only contains the default image, newer images are actually published and are supported by the operator.