Skip to content
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

chore(instrumentation): update auto-instrumentation images #3589

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

mat-rumian
Copy link
Contributor

@mat-rumian mat-rumian commented Mar 5, 2024

PR updates auto-instrumentation images used by OpenTelemetry-Operator.

Checklist

  • Changelog updated or skip changelog label added
  • Documentation updated
  • Template tests added for new features
  • Integration tests added or modified for major features

@mat-rumian mat-rumian requested a review from a team as a code owner March 5, 2024 13:25
@@ -283,19 +283,19 @@ The following table lists the configurable parameters of the Sumo Logic chart an
| `opentelemetry-operator.enabled` | Flag to control deploying OpenTelemetry Operator Helm sub-chart. | `true` |
| `opentelemetry-operator.createDefaultInstrumentation` | Flag to control creation of default Instrumentation object | `false` |
| `opentelemetry-operator.instrumentation.dotnet.extraEnvVars` | Additional environment variables for OpenTelemetry Operator Instrumentation Resource. | `{}` |
| `opentelemetry-operator.instrumentation.dotnet.image` | OpenTelemetry Operator DotNet Instrumentation image. | `ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-dotnet:0.7.0` |
| `opentelemetry-operator.instrumentation.dotnet.image` | OpenTelemetry Operator DotNet Instrumentation image. | `ghcr.io/open-telemetry/opentelemetry-operator/autoinstrumentation-dotnet:1.4.0` |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a major breaking change due to changes to HTTP semantic conventions. Shouldn't we hold back with it? At the very least, we should add a warning to the changelog about this.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, I've mixed core vs instr versioning... I will revert to the previous version used. Lack of support on our side for new sem conv will be growing pain soon.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm pretty sure 1.2.0 is the latest version without the semconv changes, so we can upgrade to that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants