chore(deps): update opentelemetry#79
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/opentelemetry
branch
4 times, most recently
from
83a2621 to
5150627
Compare
renovate
Bot
force-pushed
the
renovate/opentelemetry
branch
from
5150627 to
a400aa9
Compare
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:
0.150.1→0.152.00.148.0→0.151.00.110.0→0.112.2Release Notes
open-telemetry/opentelemetry-collector-releases (docker.io/otel/opentelemetry-collector-contrib)
v0.152.0Compare Source
🚀 New components 🚀
drainprocessor: Add drain processor to contrib distribution. (#47235)drainprocessor: Add drain processor to k8s distribution. (#47235)v0.151.0Compare Source
🚀 New components 🚀
ebpf-profiler: Add nopreceiver to the ebpf profiler distribution (#1464)💡 Enhancements 💡
packaging: Add /var/lib persistent state directories for collector RPM/DEB packages (#1396)open-telemetry/opentelemetry-operator (ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator)
v0.151.0Compare Source
🛑 Breaking changes 🛑
auto-instrumentation: Update default Java auto-instrumentation version from 1.33.6 to 2.27.0 (#4996)This is a breaking change due to HTTP semantic convention changes between versions.
Existing Instrumentation CRs using a 1.x.x version will NOT be automatically upgraded.
To upgrade, manually update the image in your Instrumentation CR after reviewing the migration guide.
See #2542 for details.
💡 Enhancements 💡
target allocator: AddsecretNamespacesfield to PrometheusCR configuration to make the namespaces watched for secrets configurable instead of hardcoding to the collector namespace. (#4999)Previously, the Target Allocator always watched the collector namespace for secrets used in
ServiceMonitor/PodMonitor basicAuth and other secret references. Now, the namespaces to watch
for secrets can be explicitly configured via
spec.prometheusCR.secretNamespaces.If not configured, no namespaces are watched for secrets.
operator: Split kubebuilder RBAC markers and restrict pod permissions to get/list/watch only (#3156)The operator does not create, update, patch, or delete Pod objects directly;
pods are managed by Deployment, DaemonSet, and StatefulSet controllers.
Also reduced targetallocators/finalizers to only the
updateverb.target allocator: Introduce kustomizaton manifests for standalone deployment (#4945)🧰 Bug fixes 🧰
auto-instrumentation: Validatespec.apacheHttpd.configPathandspec.nginx.configFilemore strictly for Instrumentations (#4925)Values from
Instrumentation.spec.apacheHttpd.configPathandInstrumentation.spec.nginx.configFileare now passed to init container scripts as positional arguments instead of being concatenated into
the shell command string, so they are no longer parsed by the shell. They're also restricted to usual Unix
path characters and limited to 256 characters.
Components
v0.150.0Compare Source
🛑 Breaking changes 🛑
auto-instrumentation: Update default .NET auto-instrumentation version from 1.2.0 to 1.15.0 (#4996)This update addresses security vulnerabilities in versions older than 1.15.0 (CVE-2026-40894, GHSA-g94r-2vxg-569j).
This is a breaking change due to HTTP semantic convention changes between versions.
Existing Instrumentation CRs using version 1.2.0 will NOT be automatically upgraded.
To upgrade, manually update the image in your Instrumentation CR after reviewing the migration guide.
See #2542 for details.
💡 Enhancements 💡
operator: Expose watch-namespace scope via the--watch-namespaceCLI flag and thewatch-namespaceconfig file field. TheWATCH_NAMESPACEenvironment variable continues to work. (#4379)auto-instrumentation: Addspec.initContainerSecurityContextto the Instrumentation CRD so users can explicitly set the security context of the auto-instrumentation init containers (Java, NodeJS, Python, DotNet, Apache HTTPD, Nginx). Addspec.go.securityContextfor overriding the Go sidecar's defaults. (#4894)When unset, existing behavior is preserved — init containers inherit the security context
of the first application container being instrumented, and the Go sidecar keeps the hardcoded
defaults required for eBPF (Privileged, RunAsUser: 0). Setting either field explicitly lets
restricted PSA environments declare the exact capabilities they want.
auto-instrumentation: Allow instrumentation upgrades to be blocked for versions containing major breaking changes. (#4646, #2542)Some instrumentation upgrades involve major breaking changes. The operator can't help with those, but it can
alert the user about them. This change makes this possible. It will also allow us to set the latest version
for new Instrumentation resources by default.
See #2542 for the primary example.
Components
v0.149.0Compare Source
💡 Enhancements 💡
collector: Add support for Gateway API HTTPRoute creation via OpenTelemetryCollector CR (#4361)operator: Added hostAliases support for OpenTelemetryCollector and TargetAllocator pods (#896)collector: Support RBAC generation fork8s_leader_electorextension (#4802)Automatically generates a ClusterRole with permissions to manage
leasesin thecoordination.k8s.ioAPI group for leader election among multiple collector replicas.collector: Add TLS security profile injection for health_check and jaeger_query extensions (#4871)When a TLS profile is configured on the cluster, the operator now injects min_version and cipher_suites
into health_check and jaeger_query extension configs
🧰 Bug fixes 🧰
auto-instrumentation: Fix instrumentation init container security context (#4848)auto-instrumentation: Fix duplicated container names validation to allow the same container name across different language instrumentations. (#4357)operator: Fix AnyConfig.DeepCopyInto performing shallow copy, causing TargetAllocator Deployment infinite reconciliation loop (#4950)AnyConfig.DeepCopyInto used maps.Copy which only copied top-level map entries, leaving nested
maps as shared references. When ApplyDefaults injected TLS profile settings (min_version) into
the collector's scrape config, it mutated the informer cache through the shared reference. This
caused the TargetAllocator config hash to alternate between two values on every reconciliation,
triggering an infinite Deployment update loop. The fix uses JSON round-tripping for a true deep copy.
opamp: Fix nil pointer dereference in OpAMP Bridge when validating a remote collector config that omits theprocessorssection (#4970)v1beta1.Config.Processorsis an optional*AnyConfig, butvalidateComponentsdereferenced it unconditionally.When a remote config without a
processorssection is applied through a bridge that hadcomponentsAllowedconfigured, it panicked and pod restarted. The nil case is now skipped during validation.
operator: Add missing RBAC permission for events.k8s.io API group (#4950)The operator uses k8s.io/client-go/tools/events which targets the events.k8s.io API group,
but the ClusterRole only granted permission for the core API group. This caused "Server rejected
event" errors when recording events on managed resources in other namespaces.
collector: Register thek8s_attributesspelling alongsidek8sattributeswhen generating RBAC from a Collector CR so either processor name produces the pods/replicasets/etc. permissions the processor needs. (#4922)The underlying processor was renamed to snake_case in
open-telemetry/opentelemetry-collector-contrib#45901 while keeping the
original spelling accepted, but the operator only parsed the camel form
and emitted no RBAC for configs using the new name.
collector: Generate RBAC for the k8s_attributes processor under its snake_case spelling, matching the camelCase k8sattributes it was renamed from. (#4922)collector: Expose prometheus receiver api_server port on collector Service and NetworkPolicy (#4949)auto-instrumentation, opamp, target allocator: Fix Env slice aliasing in Apache HTTPD, Nginx, OpAMP Bridge, and Target Allocator container builders when the spec slice has spare backing-array capacity (#4954)collector: Remove the kubebuilder default from the sts pod management policy field so it can be properlyomitempty(#4875)This field should not be set on deployment or daemonset collectors.
Components
open-telemetry/opentelemetry-helm-charts (open-telemetry/opentelemetry-helm-charts)
v0.112.2Compare Source
OpenTelemetry Operator Helm chart for Kubernetes
What's Changed
Full Changelog: open-telemetry/opentelemetry-helm-charts@opentelemetry-ebpf-instrumentation-0.9.0...opentelemetry-operator-0.112.2
v0.112.1Compare Source
OpenTelemetry Operator Helm chart for Kubernetes
What's Changed
New Contributors
Full Changelog: open-telemetry/opentelemetry-helm-charts@opentelemetry-target-allocator-0.127.3...opentelemetry-operator-0.112.1
v0.112.0Compare Source
OpenTelemetry Operator Helm chart for Kubernetes
What's Changed
Full Changelog: open-telemetry/opentelemetry-helm-charts@opentelemetry-ebpf-instrumentation-0.8.0...opentelemetry-operator-0.112.0
opentelemetry-operator 0.112.0
What's Changed
This release updates the opentelemetry-operator to version 0.150.0.
OpenTelemetry Release Notes
Chart Information
v0.111.0Compare Source
OpenTelemetry Operator Helm chart for Kubernetes
What's Changed
Full Changelog: open-telemetry/opentelemetry-helm-charts@opentelemetry-kube-stack-0.14.12...opentelemetry-operator-0.111.0
opentelemetry-operator 0.111.0
What's Changed
This release updates the opentelemetry-operator to version 0.149.0.
OpenTelemetry Release Notes
Chart Information
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.