Repository navigation
chore: update dependency open-telemetry/opentelemetry-operator to v0.162.0 - #110
Merged
Merged
Conversation
dynatrace-llc-renovate-operator
Bot
requested a review
from a team
as a code owner
October 26, 2026 21:42
mowies
approved these changes
Oct 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
v0.161.0→v0.162.0Release Notes
open-telemetry/opentelemetry-operator (open-telemetry/opentelemetry-operator)
v0.162.0Compare Source
0.162.0
🛑 Breaking changes 🛑
auto-instrumentation: Block automatic NodeJS instrumentation upgrades across 0.79.0 because of breaking HTTP, network, and database semantic convention changes. (#2542)To upgrade, manually set spec.nodejs.image to an image using instrumentation 0.79.0 or higher. See #2542 for migration details.
🚀 New components 🚀
auto-instrumentation: Add support for auto-instrumentation in PHP applications. (#932)Auto-instrumentation in PHP applications is disabled by default in operator. Users can enable it by setting the
--enable-php-instrumentationorENABLE_PHP_AUTO_INSTRUMENTATIONenvironment variable totruein operatorand setting up the annotations
instrumentation.opentelemetry.io/inject-phpandinstrumentation.opentelemetry.io/otel-php-api-version.For more information, please refer to the documentation.
auto-instrumentation: Add initial version of autoinstrumentation for ruby (#3762)Ruby auto-instrumentation is disabled by default. Enable it with
--enable-ruby-instrumentation=true.💡 Enhancements 💡
collector: Inject the cluster TLS profile's supported groups ascurve_preferencesinto generated collector configurations. (#6893)Receivers and extensions with a
tlsblock inspec.confignow getcurve_preferencesdefaulted from thecluster's TLS security profile
groups, following the same defaults-only rule asmin_versionandcipher_suites: values set by the user are never overridden.Groups without a collector
curve_preferencesspelling are logged at operator startup and not injected.🧰 Bug fixes 🧰
operator, target allocator, opamp, auto-instrumentation: Remove the distrusted emSign root CAs from the operator, target allocator, OpAMP bridge, and Python auto-instrumentation images. (#5802)The operator, target allocator, and OpAMP bridge images require Alpine
ca-certificates2026102-r0 or later.The Python auto-instrumentation image requires
certifi2026.10.19 or later and is published as0.66b1-3.The updated CA bundle removes the distrusted eMudhra emSign roots, including
emSign ECC Root CA - G3.Images are built with Go 1.27.3, which includes the
crypto/x509security fixes released on 2026-10-19.collector: Include the requesting user's UID and extra fields in the SubjectAccessReviews used to check RBAC privilege escalation. (#5659)Authorizers that rely on these fields, such as AKS with Azure RBAC for Kubernetes Authorization, denied the check
for users who held the required permissions.
collector, target allocator: Use pointer for TargetAllocator Telemetry field so omitempty works correctly with encoding/json (#5695)Go's encoding/json does not omit zero-value structs with omitempty. The non-pointer
TelemetryConfig field caused targetAllocator.telemetry to always be serialized during
server-side apply, even when not set, breaking consumers that use a CRD version without
this field.
collector: Keepservice.telemetryunchanged when the operator cannot parse it, instead of replacing it with the default Prometheus reader. (#5734)The collector accepts telemetry settings the operator does not parse, such as
resource.attributes.Such a configuration now gets an admission warning, and no default metrics reader is added to it.
Components
Configuration
📅 Schedule: (in timezone Europe/Vienna)
* 0-4,22-23 * * 1-5)* * * * 0,6)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.