feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.153.0 ) by chaplain-grimaldus[bot] · Pull Request #1688 · crutonjohn/gitops

chaplain-grimaldus · 2026-02-18T15:17:10Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Update	Change
otel-operator-source	minor	`v0.132.0` → `v0.153.0`

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

open-telemetry/opentelemetry-operator (otel-operator-source)

`v0.153.0`

Compare Source

0.153.0

🛑 Breaking changes 🛑

api: Move apis package to a separate sub-module (#4362)
- Yaml standalone functions in internal/otelconfig is moved to a methods on *Config (package apis/v1beta1)
- Move CheckTargetAllocatorPrometheusCRPolicyRules from apis/v1beta1/targetallocator_rbac.go to internal/webhook/targetallocator_rbac.go + rename it to checkTargetAllocatorPrometheusCRPolicyRules.
- OpenTelemetryCollector is not implementing the Convertible interface from sigs.k8s.io/controller-runtime/pkg/conversion, but implements 2 helper function the achieve the same functionality:
  - OtelColConvertTo(otc *OpenTelemetryCollector, dstRaw any) error
  - OtelColConvertFrom(otc *OpenTelemetryCollector, srcRaw any) error
- Move apis package to a dedicated sub-module.
target allocator: The operator.targetallocator.mtls feature gate has been removed. mTLS is now configured per-CR via spec.mtls.enabled on the TargetAllocator or Collector resource. (#5136)
Set spec.mtls.useCertManager: false to provide your own TLS secrets instead of having cert-manager provision them.

💡 Enhancements 💡

collector: Add optional spec.command to OpenTelemetryCollector to override the collector container entrypoint (#3188)
spec.command is a []string matching Pod.spec.containers[].command.
target allocator: Add allowInsecureAuthSecrets option to serve auth secret values over plain HTTP without mTLS (#3746)
Adds a new allowInsecureAuthSecrets field to both the TargetAllocator CRD and the
embedded TargetAllocator in the OpenTelemetryCollector CRD. When enabled, auth secret
values (e.g. basicAuth passwords) are served over plain HTTP instead of being masked.
This is useful when transport security is handled by a service mesh or equivalent.

🧰 Bug fixes 🧰

must-gather: Fix must-gather output to produce omc-compatible directory layout and correct YAML serialization (#4965)
Previously collected files used a per-collector directory with kind-prefixed filenames (e.g. namespaces/<ns>/<collector-name>/deployment-<name>.yaml),
which omc cannot parse. Output now follows the standard omc layout (namespaces/<ns>/<api-group>/<resource-plural>/<name>.yaml).
Also fixes missing apiVersion/kind fields in serialized YAML, incorrect default output directory, and adds collection of CRDs and OpAMPBridge resources.
opamp: Skip OpenTelemetryCollector instances with a non-nil DeletionTimestamp when building EffectiveConfig (#5170)
ListInstances returns objects with DeletionTimestamp set until finalizers complete.
Reporting them as effective races with the bridge's own Delete calls in applyRemoteConfig.
collector: Fix Service reconciliation to propagate trafficDistribution, internalTrafficPolicy, ipFamilies, and ipFamilyPolicy changes (#5141)

Components

`v0.152.0`

Compare Source

0.152.0

🛑 Breaking changes 🛑

api: Move config parsing and CRD metrics from apis to internal package (#4362)
- Methods on *Config (package apis/v1beta1) converted to standalone functions in internal/otelconfig, now taking *v1beta1.Config as the first parameter:
  - GetEnabledComponents, GetReceiverPorts, GetExporterPorts, GetExtensionPorts, GetReceiverAndExporterPorts, GetAllPorts, GetEnvironmentVariables, GetAllRbacRules, ApplyDefaults, GetLivenessProbe, GetReadinessProbe, GetStartupProbe, Yaml, NullObjects
- Methods on *Service converted to functions in internal/otelconfig:
  - MetricsEndpoint, GetTelemetry
  - ApplyDefaults → renamed to ServiceApplyDefaults
- Method on *Telemetry converted to function:
  - ToAnyConfig → renamed to TelemetryToAnyConfig
- Functions moved from apis/v1beta1 to internal/metrics with renames:
  - BootstrapMetrics → Bootstrap
  - NewMetrics(prv, ctx, cl) → New(ctx, prv, cl) (parameter reorder: ctx now first)
- Types moved out of apis/v1beta1:
  - MetricsConfig, Telemetry → internal/otelconfig
  - Metrics → internal/metrics

💡 Enhancements 💡

target allocator: Add support for dropping ServiceMonitor/PodMonitor endpoints that reference arbitrary files (#5104)

auto-instrumentation: Allow to run the mutating webhook using static configuration, without the need for CRDs. (#4201)

With this change, you can deploy the manager as a mutating webhook without setting up a v1alpha1.Instrumentation custom resource
or the v1alpha1.Instrumentation CRD.

Instead, you can now set up instrumentation by configuring the manager via its config file with these settings:

  ignore-missing-collector-crds: true 
  enable-instrumentation-crds: false # Ignore that the CRD is not registered.
  enable-multi-instrumentation: false
  instrumentations: # Static configuration for our instrumentation
    spec:
      exporter:
        endpoint: http://collector.default.svc:4318
      propagators:
        - tracecontext
        - baggage
        - b3
      java:
        image: "java-autoinstrumentation:dev"

target allocator: Improve the error message when the target allocator is enabled but the Prometheus receiver is not named exactly "prometheus". (#5017)

When only named instances such as "prometheus/otelcol" are present, the error now lists them and explains that a receiver named exactly "prometheus" is required.

🧰 Bug fixes 🧰

collector: Remove unnecessary RBAC permissions from the events receiver. (#5073)
collector: Fix when configuring a gRPC port for the jaeger_query extension, the collector-extension Service only generates an HTTP port and is missing the gRPC port. (#4912)
collector: Explicitly set without_type_suffix, without_units, and without_scope_info to false on the operator-injected Prometheus telemetry reader. (#5075)

Preserves historical metric names. Without this, users upgrading to a collector containing open-telemetry/opentelemetry-collector#15027 would see operator-managed collector metric names silently change shape. Added alpha feature gate operator.collector.usedefaulttelemetryshape (off by default) to opt into collector defaults instead. The gate will be promoted to beta (on by default) in a future release.
target allocator: Fix scrapeClass tlsConfig fields being silently dropped in target allocator config. (#5101)

scrapeClasses with tlsConfig like the following had their TLS fields silently dropped
when passed to the target allocator:
scrapeClasses:
- name: tls-config
tlsConfig:
caFile: /scrapeclass-ca.pem
insecureSkipVerify: true
collector: Restrict automatic RBAC from users without the necessary permissions (#5105)

If the operator has permission to create ClusterRoles and ClusterRoleBindings, it sets up RBAC
for collectors automatically based on their configuration.
If a user tries to create an OpenTelemetryCollector whose permissions would be automatically
generated this way, and the user doesn't have the permissions themselves, it will be rejected.
If the collector tries to use an existing ServiceAccount, only the permissions missing from
that ServiceAccount are checked this way.
collector: Skip provisioning Services, Ingress, NetworkPolicy, and HPA for sidecar mode collectors since the operator does not control the Pod lifecycle in that mode. PodMonitors are still provisioned when metrics are enabled. (#4934)

Components

`v0.151.0`

Compare Source

0.151.0

🛑 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: Add secretNamespaces field 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 update verb.
target allocator: Introduce kustomizaton manifests for standalone deployment (#4945)

🧰 Bug fixes 🧰

auto-instrumentation: Validate spec.apacheHttpd.configPath and spec.nginx.configFile more strictly for Instrumentations (#4925)
Values from Instrumentation.spec.apacheHttpd.configPath and Instrumentation.spec.nginx.configFile
are 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.0`

Compare Source

0.150.0

🛑 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-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 #2542 for the primary example.

Components

`v0.149.0`

Compare Source

0.149.0

💡 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 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

🧰 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 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.

Components

`v0.148.0`

Compare Source

0.148.0

💡 Enhancements 💡

collector: make the statefulset PodManagementPolicy configurable (#4875)

Components

`v0.147.0`

Compare Source

0.147.0

🛑 Breaking changes 🛑

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)

🧰 Bug fixes 🧰

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.

Components

`v0.146.0`

Compare Source

0.146.0

💡 Enhancements 💡

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.

🧰 Bug fixes 🧰

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.

Components

`v0.145.0`

Compare Source

0.145.0

🛑 Breaking changes 🛑

collector: Remove operator.collector.default.config feature gate (#4473)

🚀 New components 🚀

clusterObservability: Inital implementation of ClusterObservability CRD (#3820)
This change provides an initial implementation of the Cluster Observability CRD and operator control loop.
Reconcilation is disabled by default.
Currently, the CRD is not included in the operator bundle and must be installed manually.
To enable reconciliation, enable the --feature-gates=+operator.clusterobservability feature gate.

💡 Enhancements 💡

target allocator: Add readiness and liveness probe configurations for target allocator CRD (#4639)
target allocator: Make the least-weighted target allocation strategy take job name into account. (#3128)
Uses job name instead of "first match" to when number of targets is equal. The effect is to spread out targets with the same job name across collectors.

🧰 Bug fixes 🧰

target allocator: Fix TLS certificate hot-reload for mTLS connections (#4368)
The Target Allocator now automatically reloads TLS certificates when they are renewed
by cert-manager. Previously, certificate renewals required a pod restart because
certificates were only loaded once at startup. The fix uses fsnotify to watch the
certificate directory and dynamically reloads certificates via the GetCertificate
callback, enabling seamless certificate rotation without downtime.
collector: Configure collector to reload client certificate periodically (#4657)
When the collector connects to the target allocator over mTLS, certificates were not automatically reloaded after expiration. This adds reload_interval to the TLS configuration, enabling the Prometheus receiver to periodically reload certificates from disk.

The default interval of 5 minutes provides a good balance between picking up renewed certificates promptly and avoiding unnecessary overhead.
operator: Set Kubernetes API server egress network policy port dynamically. (#4411)
The operator network policy egress rule for the Kubernetes API server was hardcoded to port 6443.
This PR uses uses endpointslices.discovery.k8s.io -n default kubernetes to get the port and IP addresses of the Kubernetes API server
for the operator egress network policy.

Components

`v0.144.0`

Compare Source

0.144.0

💡 Enhancements 💡

operator: change operator args in bundle to env variables (#4612)
The default configuration in the OLM bundle has been changed from command-line arguments to environment variables,
making it easily overwritable when deployed using OLM's Subscription config. Command-line flags continue to work.
All Config struct fields now support environment variable configuration.

Configuration set via the Subscription's config section will persist and be reapplied after operator upgrades.

Example of overriding configuration via OLM Subscription:
```
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: opentelemetry-operator
spec:
  channel: stable
  name: opentelemetry-operator
  source: operatorhubio-catalog
  sourceNamespace: olm
  config:
    env:
    - name: FEATURE_GATES
      value: "operator.networkpolicy,operand.networkpolicy"
    - name: ENABLE_GO_AUTO_INSTRUMENTATION
      value: "true"
    - name: METRICS_SECURE
      value: "false"
```

🧰 Bug fixes 🧰

collector: Fix PodDisruptionBudget using all labels instead of selector labels, preventing PDB breakage during rollouts (#4623)
Use stable selector labels instead of all CR labels to prevent PDB breakage when mutable labels change during rollouts.
auto-instrumentation: Fix NGINX and Apache instrumentation init container creation to avoid copying init-container-incompatible fields. (#3729)
The NGINX and Apache instrumentation init containers are now created from scratch instead of
cloning the main container, preventing probes, lifecycle hooks, and resize policies from being
applied to init containers.

Components

`v0.143.0`

Compare Source

0.143.0

🧰 Bug fixes 🧰

operator: Fix operator ServiceMonitor not created on OpenShift (#4603)
Two issues prevented the operator ServiceMonitor from being created on OpenShift:
1. The OpenShift kustomize patches were incorrectly overwriting operator args, removing flags like --create-sm-operator-metrics=true.
2. The prometheus-operator library SchemeHTTPS constant uses uppercase "HTTPS" which is rejected by ServiceMonitor CRD validation.

Components

`v0.142.0`

Compare Source

0.142.0

🛑 Breaking changes 🛑

operator: Remove kube-rbac-proxy from operator deployment and use controller-runtime built-in auth (#3369)
The operator now uses controller-runtime built-in auth for the metrics server. It is disabled by default.
The client accessing the metrics endpoint must have the following RBAC rule nonResourceURLs: "/metrics", verbs: get.
Which didn't change from the previous approach of using kube-rbac-proxy.

This changes adds following flags to the operator:
metrics-secure - enables authentication and authorization for the metrics server. If no TLS certificates are provided, self signed certificates will be generated.
metrics-tls-cert-file - TLS certificate file for the metrics server
metrics-tls-key-file - TLS private key file for the metrics server

This change changes the following flags on the operator:
--metrics-addr - changes from 127.0.0.1:8080 to :8443 which matches the operator's metrics service port.

💡 Enhancements 💡

target allocator: Add support for prometheus scrape classes (#3600)
Added support for configuring scrapeClasses when using the PrometheusCR-feature of the target allocator. The format of the scrapeClasses array is exactly as same as spec.scrapeClasses of the Prometheus CRD.
operator: Add support for Kubernetes 1.35 (#4575)
collector: exposes the spec.hostPID field for the collector. (#4214)
This will allow to set the spec.HostPID field for the collector. By default this the field is false.

🧰 Bug fixes 🧰

target allocator: Fix CA certificate race condition with client cert renewals by extending its duration and and renewal attempt. (#4441)
The CA certificate now has a 2-year duration (instead of the default 90 days) to prevent race conditions
where client and server certificates could be signed by different CA versions during simultaneous renewal.
This ensures the CA remains stable while dependent certificates renew regularly.
collector: Add finalizers to OpenTelemetryCollector CR only when cluster roles and bindings for SA are created by Operator. (#4367)
Finalizer usage was restricted to cluster scoped resources only. Namespaced resources no longer receive finalizers,
preventing blocked namespace deletion if the operator is removed first. The change aligns finalizer behavior with
cluster-level RBAC availability, ensuring finalizers are applied only when the operator has the required
cluster scoped permissions.
config: Fix manager logger initialization (#4584)
Apply config before setting up logger to configure it properly.
operator: Fix the --annotations-filter and --labels-filter CLI flags. (#4594)

Components

`v0.141.0`

Compare Source

0.141.0

💡 Enhancements 💡

collector: Ensure the collector container is always listed first in the podspec (#4548)
This is so tools like kubectx logs will always default to the collector container instead of any additional containers that are configured.
target allocator: make evaluation_interval configurable for Prometheus CR watcher (#4520)
operator: Support for Kubernetes 1.34 version. (#4415)

Components

`v0.140.0`

Compare Source

0.140.0

🛑 Breaking changes 🛑

operator: Remove native sidecar feature gate (#4451)
The feature gate operator.sidecarcontainers.native has been removed.
It was introduced in v0.111.0, enabled by default since v0.132.0, and marked as stable in v0.139.0.
Native sidecars are now automatically enabled on Kubernetes v1.29+ without requiring a feature gate.
If you were explicitly enabling or disabling this feature gate with --feature-gates=+operator.sidecarcontainers.native,
you must remove that flag.

💡 Enhancements 💡

collector: Promote the operator.golang.flags feature flag to Beta (#4452)
The operator will set the GOMEMLIMIT and GOMAXPROCS environment variables based
on the pod configuration of the collector container by default.
operator: Use pod and namespace label selector in operator NetworkPolicy for the API server Egress on OpenShift. (#4490)
On OpenShift use pod ("apiserver": "true") and namespace (kubernetes.io/metadata.name": "openshift-kube-apiserver")
label selectors in API server Egress network policy.

🧰 Bug fixes 🧰

auto-instrumentation: Fixes the precedence of spec.env in Instrumentation CR so global env vars correctly override defaults. (#4068)
Previously, environment variables set under spec.env were ignored in favor of default instrumentation config,
unless duplicated in each language block. This change ensures the correct order of precedence is applied:
language-specific env vars > spec.env > defaults.
collector: Fix mounting spec.configmaps in sidecar mode (#4489)
Configmaps defined in spec.configmaps were not properly mounted in the sidecar mode.
github action: Remove unused VERSION and VERSION_DATE environment variables from publish workflows (#4470)
Removed the unused "Read version" step that set VERSION and VERSION_DATE environment variables in both publish-target-allocator.yaml and publish-operator-opamp-bridge.yaml workflows. These variables were never referenced anywhere in the workflows.

Components

`v0.139.0`

Compare Source

0.139.0

💡 Enhancements 💡

operator: Promote the operator.sidecarcontainers.native feature flag to Stable. (#4451)
By default, the operator will continue to use native sidecars on Kubernetes versions
newer than 1.29. This behaviour cannot be disabled.
The operator flag will be removed with the release of version 0.140.0.
collector: Promote the operator.collector.default.config feature gate to Stable (#4453)

Components

`v0.138.0`

Compare Source

0.138.0

💡 Enhancements 💡

collector: Migrate simple OpenTelemetryCollector validations from the webhook to CRD annotations so Kubernetes enforces them server-side. ()

🛑 Breaking changes 🛑

target allocator: Remove the operator.collector.targetallocatorcr feature flag (#2422)
This behavior has been enabled by default since version 0.127.0.

🚩 Deprecations 🚩

auto-instrumentation: Deprecate VolumeSizeLimit in the Instrumentation CRD (#3382)
- The volumeSizeLimit field

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (in timezone America/New_York)

Branch creation
- At any time (no schedule defined)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

…3.0 )

chaplain-grimaldus Bot added the type/minor label Feb 18, 2026

chaplain-grimaldus Bot force-pushed the renovate/otel-operator-source-0.x branch from 4ec8a38 to ebc8005 Compare February 18, 2026 18:13

chaplain-grimaldus Bot changed the title ~~feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.144.0 )~~ feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.145.0 ) Feb 18, 2026

chaplain-grimaldus Bot force-pushed the renovate/otel-operator-source-0.x branch from ebc8005 to 687882f Compare March 9, 2026 15:19

chaplain-grimaldus Bot changed the title ~~feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.145.0 )~~ feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.146.0 ) Mar 9, 2026

chaplain-grimaldus Bot force-pushed the renovate/otel-operator-source-0.x branch from 687882f to 586cb20 Compare March 18, 2026 12:13

chaplain-grimaldus Bot changed the title ~~feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.146.0 )~~ feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.147.0 ) Mar 18, 2026

chaplain-grimaldus Bot force-pushed the renovate/otel-operator-source-0.x branch from 586cb20 to ef3df96 Compare March 23, 2026 12:12

chaplain-grimaldus Bot changed the title ~~feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.147.0 )~~ feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.148.0 ) Mar 23, 2026

chaplain-grimaldus Bot force-pushed the renovate/otel-operator-source-0.x branch from ef3df96 to 210415d Compare April 23, 2026 14:43

chaplain-grimaldus Bot changed the title ~~feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.148.0 )~~ feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.149.0 ) Apr 23, 2026

chaplain-grimaldus Bot force-pushed the renovate/otel-operator-source-0.x branch from 210415d to f05f955 Compare April 27, 2026 17:31

chaplain-grimaldus Bot changed the title ~~feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.149.0 )~~ feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.150.0 ) Apr 27, 2026

chaplain-grimaldus Bot force-pushed the renovate/otel-operator-source-0.x branch from f05f955 to 0d643a3 Compare May 12, 2026 20:32

chaplain-grimaldus Bot changed the title ~~feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.150.0 )~~ feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.151.0 ) May 12, 2026

chaplain-grimaldus Bot force-pushed the renovate/otel-operator-source-0.x branch from 0d643a3 to e60d29d Compare May 25, 2026 21:25

chaplain-grimaldus Bot changed the title ~~feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.151.0 )~~ feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.152.0 ) May 25, 2026

chaplain-grimaldus Bot changed the title ~~feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.152.0 )~~ feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.152.0 ) - autoclosed Jun 10, 2026

chaplain-grimaldus Bot closed this Jun 10, 2026

chaplain-grimaldus Bot deleted the renovate/otel-operator-source-0.x branch June 10, 2026 16:19

feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.15…

9be45ec

…3.0 )

chaplain-grimaldus Bot changed the title ~~feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.152.0 ) - autoclosed~~ feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.153.0 ) Jun 10, 2026

chaplain-grimaldus Bot reopened this Jun 10, 2026

chaplain-grimaldus Bot force-pushed the renovate/otel-operator-source-0.x branch from e60d29d to 9be45ec Compare June 10, 2026 18:04

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.153.0 )#1688

feat(deps): update dependency otel-operator-source ( v0.132.0 → v0.153.0 )#1688
chaplain-grimaldus[bot] wants to merge 1 commit into
mainfrom
renovate/otel-operator-source-0.x

chaplain-grimaldus Bot commented Feb 18, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

chaplain-grimaldus Bot commented Feb 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

0.153.0

🛑 Breaking changes 🛑

💡 Enhancements 💡

🧰 Bug fixes 🧰

Components

0.152.0

🛑 Breaking changes 🛑

💡 Enhancements 💡

🧰 Bug fixes 🧰

Components

0.151.0

🛑 Breaking changes 🛑

💡 Enhancements 💡

🧰 Bug fixes 🧰

Components

0.150.0

🛑 Breaking changes 🛑

💡 Enhancements 💡

Components

0.149.0

💡 Enhancements 💡

🧰 Bug fixes 🧰

Components

0.148.0

💡 Enhancements 💡

Components

0.147.0

🛑 Breaking changes 🛑

🧰 Bug fixes 🧰

Components

0.146.0

💡 Enhancements 💡

🧰 Bug fixes 🧰

Components

0.145.0

🛑 Breaking changes 🛑

🚀 New components 🚀

💡 Enhancements 💡

🧰 Bug fixes 🧰

Components

0.144.0

💡 Enhancements 💡

🧰 Bug fixes 🧰

Components

0.143.0

🧰 Bug fixes 🧰

Components

0.142.0

🛑 Breaking changes 🛑

💡 Enhancements 💡

🧰 Bug fixes 🧰

Components

0.141.0

💡 Enhancements 💡

Components

0.140.0

🛑 Breaking changes 🛑

💡 Enhancements 💡

🧰 Bug fixes 🧰

Components

0.139.0

💡 Enhancements 💡

Components

0.138.0

💡 Enhancements 💡

🛑 Breaking changes 🛑

🚩 Deprecations 🚩

Configuration

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

chaplain-grimaldus Bot commented Feb 18, 2026 •

edited

Loading