NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules · #1051 by repository stars
Last release today
07 Oct 2026
Ships on a steady schedule
a new release about every 9 days
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
1550 releases · first in 2019
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.
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
target-allocator: Fixes the incorrect k8s version for the traffic distribution feature.
target-allocator: Fixes the incorrect k8s version for the traffic distribution feature. (#4394)collector: Fix statefulset serviceName field change handling. (#4371)
The Operator 0.129.1 introduced a new feature which allows setting the serviceName of the collector statefulset (#4041).
This feature introduced two issues:
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, target allocator: Add TrafficDistribution support for OpenTelemetryCollector and TargetAllocator Services (#4285) The TrafficDistribution f
collector, target allocator: Add TrafficDistribution support for OpenTelemetryCollector and TargetAllocator Services (#4285)
The TrafficDistribution field is now available in OpenTelemetryCollector and TargetAllocator.
This field allows setting the traffic distribution policy for Kubernetes Services.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
target allocator: Add CollectorTargetReloadInterval option to configure the interval at which the Prometheus receiver reloads targets from the target
target allocator: Add CollectorTargetReloadInterval option to configure the interval at which the Prometheus receiver reloads targets from the target allocator (#4095)collector: Always return a valid OpenTelemetryCollector configuration during v1beta1 conversion. (#4288)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: Remove opencensus receiver from parsing logic as it is no longer supported in OpenTelemetry Collector (#4239) The opencensus receiver has b
collector: Remove opencensus receiver from parsing logic as it is no longer supported in OpenTelemetry Collector (#4239)
The opencensus receiver has been removed from the operator's receiver parsing logic.
Since 2025-02-14 its no longer supported and got removed from the Collector Distributions.collector: enable native sidecar on OpenShift 4.16+ with k8s version newer then v1.29 by default. (#4247)
collector: Use native sidecar on k8s 1.29+ (#3356)
The operator will automatically use native sidecars whenever a Kubernetes
version 1.29 or higher is discovered.
The usage of native sidecars can be disabled with --feature-gates=-sidecarcontainers.native.
See: https://kubernetes.io/blog/2023/08/25/native-sidecar-containers/
collector: Add network policy for the collector. (#4231)
This change adds a network policy to the collector to allow traffic to all collector receivers and egress traffic from the collector pod.
The collector network policy can be enabled in the collector CR.
spec:
networkPolicy:
enabled: true
By default it is disabled, however the default value is configured with a feature gate --feature-gates=operand.networkpolicy.
The feature gate will be enabled in the future releases.
operator: Operator now creates a NetworkPolicy to restrict access to the operator pod. (#4230)
The operator network policy can be enabled with --feature-gates=+operator.networkpolicy.
The feature gate is disabled by default and it will be enabled in the future releases.
Following APIs are allowe: ingress on port 9443 (webhook), 8080 (metrics port), 8443 (metrics RBAC proxy) and egress on port 6443 (API server).
target allocator: Add network policy for the target allocator. (#4231)
This change adds a network policy to the target allocator which allows traffic to the port 8080 and outgoing traffic to the API server.
The target allocator network policy can be enabled in the target allocator CR.
spec:
networkPolicy:
enabled: true
By default it is disabled, however the default value is configured with a feature gate --feature-gates=operand.networkpolicy.
The feature gate will be enabled in the future releases.
opamp: Correlates the OpAMP data from the proxy server with the bridge's own OpAMP data. (#3837)
collector: k8sattributes: Add automatic RBAC for new service.name resource attribute generator (#4131)
The k8sattributes processor recently added support for automatic service.name resource attribute generation.
This change ensures that when service.name is configured in the k8sattributes processor, the operator
automatically adds the necessary RBAC rules for replicasets access, which is required for extracting
k8s.deployment.name.
opamp: fixes a bug where the bridge deployment wouldn't rollout on a config change. (#4020)
collector: Fix a Deployment restart issue caused when the HPA settings changed, the webhook would modify spec.replicas. (#2585)
collector: Operator no longer overwrites ingress annoations on change (#4322)
The operator now respects external manipulations of the Ingress object — instead of
overwriting annotations it respects existing to prevent annotation-overwrite issues
that caused reconciliation loops with external controllers (e.g., Rancher).
collector, target allocator, opamp: Remove unnecessary cert-manager CA annotation from CRDs (#4321)
Remove annotation cert-manager.io/inject-ca-from from all OpenShift CRD manifests. The CRDs on OpenShift are installed via OLM which handles the CA injection.
The annotation is also not needed for non-OpenShift installations on CRDs that do not have a conversion webhook.
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
operator: Drop support for Kubernetes 1.23 and 1.24
operator: Drop support for Kubernetes 1.23 and 1.24 (#4104)collector: Add support for extraLabels in ServiceMonitor creation (#4138)
Added extraLabels field to MetricsConfigSpec in v1beta1 API to allow custom labels on ServiceMonitor resources.
This enables users to add additional labels to ServiceMonitors created by the operator for better organization and filtering.
manager, target-allocator, opamp-bridge, must-gather: add -trimpath when building binaries (#4078)
collector, targer allocator, opamp: Require Go 1.24+ to build the collector, target allocator, and opamp. (#4173)
collector: Added RBAC permissions for config.extensions.k8s_observer. (#4113)
Generating RBAC rules for the k8s_observer extension in the OpenTelemetry Collector when used in the operator.
The change addresses the issue where the collector lacked necessary permissions to list and watch Kubernetes resources.
auto-instrumentation: Upgrade urllib3 upper limit following Python 3.8 support drop (#3712)
collector: added check for maxReplica when minReplica is set in autoscaler (#4160)
When using the AutoScaler, maxReplica must be set when minReplica is set.target allocator: check CRD availability before registering informers (#3987)target allocator: Allow collector to use TLS Config from Target Allocator with ScrapeConfig (#3724)
This change allows the target allocator to configure TLS Config for a collector using the ScrapeConfig.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
Your coding agent can read these notes before it upgrades. Set up the MCP server →