NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #1081 by repository stars
Latest stable
v0.162.0
Last release 14 days ago
08 Nov 2026
Ships on a steady schedule
a new release about every 8 days
Nearly every release is documented
notes for 60 of the last 60 stable releases
1 version withdrawn
withdrawn after publishing
7 years old
1666 releases · first in 2019
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
…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…
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 https://github.com/open-telemetry/opentelemetry-operator/issues/2542 for details.operator: Expose watch-namespace scope via the --watch-namespace CLI flag and the watch-namespace config file field. The WATCH_NAMESPACE environment variable continues to work. (#4379)
auto-instrumentation: Add spec.initContainerSecurityContext to the Instrumentation CRD so users can explicitly set the security context of the auto-instrumentation init containers (Java, NodeJS, Python, DotNet, Apache HTTPD, Nginx). Add spec.go.securityContext for 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 https://github.com/open-telemetry/opentelemetry-operator/issues/2542 for the primary example.
Nothing published for this version
Nothing published for this version
collector: Add support for Gateway API HTTPRoute creation via OpenTelemetryCollector CR
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 for k8s_leader_elector extension (#4802)
Automatically generates a ClusterRole with permissions to manage leases in the coordination.k8s.io API 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
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 the processors section (#4970)
v1beta1.Config.Processors is an optional *AnyConfig, but validateComponents dereferenced it unconditionally.
When a remote config without a processors section is applied through a bridge that had componentsAllowed
configured, 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 the k8s_attributes spelling alongside k8sattributes when 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 properly omitempty (#4875)
This field should not be set on deployment or daemonset collectors.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
collector: make the statefulset PodManagementPolicy configurable
collector: make the statefulset PodManagementPolicy configurable (#4875)Nothing published for this version
Nothing published for this version
Nothing published for this version
apis/v1beta1: Move webhooks from the apis/v1beta1 package to the internal package internal/webhook
apis/v1beta1: Move webhooks from the apis/v1beta1 package to the internal package internal/webhook (#4846)v1alpha1: Move webhooks from the apis/v1alpha1 package to the internal package internal/webhook (#4837)target allocator: Fix Service Monitor/Pod Monitor in TargetAllocator doesnt pick up updates to secrets (#4091)
Fixes issue where service/pod Monitors don't pick up updates to secrets.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
target allocator: Expose missing Prometheus CR fields in the Operator API (#1934) Added podMonitorNamespaceSelector, serviceMonitorNamespaceSelector,
target allocator: Expose missing Prometheus CR fields in the Operator API (#1934)
Added podMonitorNamespaceSelector, serviceMonitorNamespaceSelector, scrapeConfigNamespaceSelector,
probeNamespaceSelector, evaluationInterval, and scrapeProtocols to the prometheusCR
configuration within the TargetAllocator and OpenTelemetryCollector
APIs to achieve feature parity with the underlying Target Allocator.
collector: Add the hostUsers field to OpenTelemetryCommonFields to enable toggling support for isolating pod processes under a separate user namespace (#4366)
auto-instrumentation: Add support for initContainers to instrumentation injector (#3308)
Add support for instrumenting init containers.
Init container support is available for Java, Python, Node.js, .NET and SDK-only, and works using the same annotation as for regular containers.
operator, collector: Allow operator to get TLS settings from OpenShift APIServer CR and configure operands TLS settings. (#4669)
Added operator flag --tls-cluster-profile which obtains the TLS min version and cipher suites from the OpenShift APIServer cluster custom resource (CR).
It overrides the --tls-min-version and --tls-cipher-suites flags if set.
The flags is disabled by default on Kubernetes and enabled on OpenShift.
Added operator flag --tls-configure-operands which configures operands TLS settings (min version, cipher suites)
based on the supplied operator TLS flags (--tls-cipher-suites and --tls-min-version) or from the OpenShift APIServer CR
if --tls-cluster-profile is enabled.
The flag is disabled by default on Kubernetes and enabled on OpenShift.
The --tls-min-version defaults to TLSv1.2 which matches the collector's default.
The --tls-cipher-suites is empty by default which matches the collector's default.
Therefore enabling --tls-configure-operands with the default TLS flags should not change the collector's behavior.
operator: Add webhook server readiness check to the operator's /readyz endpoint so the pod is not marked ready before the webhook server is listening. (#3772)
Previously the readiness probe used only healthz.Ping, causing a race where CRs
created right after deployment could hit "connection refused" from the webhook.
Now the readyz endpoint includes a check using controller-runtime's
StartedChecker which verifies the webhook TLS listener is actually accepting connections.
collector: Remove legacy finalizer from OpenTelemetryCollector CR when RBAC not available. (#4769)
Finalizer usage was restricted to cluster scoped resources only. Legacy finalizer added by OpenTelemetry Operator
<= v0.141.0 still blocks namespace deletion if the operator is removed first. The change removes finalizer with
cluster-level RBAC availability.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.