[8.19] (backport #11001) [otel/kube-stack] Update EDOT SDK k8s auto-instrumentation images to their latest versions #11333
+6
−6
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.
Update the versions of the EDOT language SDK images being used with the OTel Operator.
Bump EDOT SDKs to latest versions
Update Elastic OTEL Java image in values.yaml
change detected: * key "$.instrumentation.java.image" updated from "docker.elastic.co/observability/elastic-otel-javaagent:1.6.0" to "docker.elastic.co/observability/elastic-otel-javaagent:1.7.0", in file "deploy/helm/edot-collector/kube-stack/managed_otlp/values.yaml" * key "$.instrumentation.java.image" updated from "docker.elastic.co/observability/elastic-otel-javaagent:1.6.0" to "docker.elastic.co/observability/elastic-otel-javaagent:1.7.0", in file "deploy/helm/edot-collector/kube-stack/values.yaml"
v1.7.0
Update Elastic OTEL Python image in managed_otlp/values.yaml
change detected: * key "$.instrumentation.python.image" updated from "docker.elastic.co/observability/elastic-otel-python:1.9.0" to "docker.elastic.co/observability/elastic-otel-python:1.10.0", in file "deploy/helm/edot-collector/kube-stack/managed_otlp/values.yaml" * key "$.instrumentation.python.image" updated from "docker.elastic.co/observability/elastic-otel-python:1.9.0" to "docker.elastic.co/observability/elastic-otel-python:1.10.0", in file "deploy/helm/edot-collector/kube-stack/values.yaml"
v1.10.0
Update Elastic OTEL Node.js image in values.yaml
change detected: * key "$.instrumentation.nodejs.image" updated from "docker.elastic.co/observability/elastic-otel-node:1.5.0" to "docker.elastic.co/observability/elastic-otel-node:1.6.0", in file "deploy/helm/edot-collector/kube-stack/values.yaml" * key "$.instrumentation.nodejs.image" updated from "docker.elastic.co/observability/elastic-otel-node:1.5.0" to "docker.elastic.co/observability/elastic-otel-node:1.6.0", in file "deploy/helm/edot-collector/kube-stack/managed_otlp/values.yaml"
v1.6.0
## Changelog ### Features and enhancements * Add support for `ELASTIC_OTEL_OPAMP_HEADERS` environment variable for setting headers for OpAMP requests. This typically would be used to specify authorization for a given `ELASTIC_OTEL_OPAMP_ENDPOINT`, e.g.: `export ELASTIC_OTEL_OPAMP_HEADERS="Authorization=ApiKey sekrit"`. [#1069](https://github.com/elastic/elastic-otel-node/issues/1069) * HTTP exporters now accept TLS configuration via the env vars `OTEL_EXPORTER_OTLP_CERTIFICATE`, `OTEL_EXPORTER_OTLP_CLIENT_KEY` and `OTEL_EXPORTER_OTLP_CLIENT_CERTIFICATE`. The signal specific vars (`OTEL_EXPORTER_OTLP_TRACES_CERTIFICATE`, ...) are also taken into account. * Prepend EDOT Node.js product identifier in the `user-agent` for all HTTP and GRPC exporters. ([#1104](https://github.com/elastic/elastic-otel-node/pull/1104)) * Switch back to the upstream resource detector `@opentelemetry/resource-detector-gcp` which covers more environments thanks to Google's [contribution](https://github.com/open-telemetry/opentelemetry-js-contrib/pull/3007). * Add support for dynamic configuration of the sampling rate of the default logger via the `sampling_rate` variable in Central Configuration. [#1070](https://github.com/elastic/elastic-otel-node/pull/1070) While this is supported in the EDOT Node.js SDK, it will only be present in the "Agent Configuration" UI of Kibana version 9.3 and later. ### Fixes * Update to latest `@opentelemetry/*` dependencies ([#1104](https://github.com/elastic/elastic-otel-node/pull/1104)), which includes a couple of fixes: * a bug in `@opentelemetry/[email protected]` prevented to set the `user-agent` header in metadata. A [change in the exporter configuration](https://github.com/open-telemetry/opentelemetry-js/pull/5928) fixed it. * the context manager and propagation setup is the first thing at the start of the SDK. This prevents detectors from [leaking telemetry](https://github.com/open-telemetry/opentelemetry-js-contrib/issues/2320) since they get the right context. --- [README](https://github.com/elastic/elastic-otel-node/tree/main/packages/opentelemetry-node#readme) | [Full Release Notes](https://github.com/elastic/elastic-otel-node/blob/main/docs/release-notes/index.md) | [Breaking Changes](https://github.com/elastic/elastic-otel-node/blob/main/docs/release-notes/breaking-changes.md)Created automatically by Updatecli
Options:
Most of Updatecli configuration is done via its manifest(s).
Feel free to report any issues at github.com/updatecli/updatecli.
If you find this tool useful, do not hesitate to star our GitHub repository as a sign of appreciation, and/or to tell us directly on our chat!
This is an automatic backport of pull request #11001 done by [Mergify](https://mergify.com).