build(deps): Upgrade otelcollector to v0.145.0#1419
Closed
azure-monitor-assistant[bot] wants to merge 1 commit intomainfrom
Closed
build(deps): Upgrade otelcollector to v0.145.0#1419azure-monitor-assistant[bot] wants to merge 1 commit intomainfrom
azure-monitor-assistant[bot] wants to merge 1 commit intomainfrom
Conversation
Contributor
Author
View build errors |
Contributor
|
This PR is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Contributor
|
This PR was closed because it has been stalled for 12 days with no activity. |
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 upgrades the otelcollector to the latest version available for the opentelemetry-collector and opentelemetry-operator.
It was automatically generated by the GitHub Actions workflow.
The summary of the OSS changelog is below:
Prometheusreceiver Changes
v0.144.0 to v0.145.0
Generated on: 2026-02-19 07:24:34
v0.145.0
receiver/prometheus: Promotereceiver.prometheusreceiver.RemoveReportExtraScrapeMetricsConfigfeature gate to beta (#44181) Thereport_extra_scrape_metricsconfiguration option is now ignored by default. Extra scrape metrics are instead controlled by thereceiver.prometheusreceiver.EnableReportExtraScrapeMetricsfeature gate and the Prometheus upstream configuration available inpromconfig(either globally or per-scrape config).receiver/prometheus: Support removable Prometheus service discoveries via Go build tags. (#44406) Prometheus service discoveries can now be removed at build time when building the collector with OCB (OpenTelemetry Collector Builder). Use thebuild_tagsoption in the builder configuration to pass Go build tags such asremove_all_sdto exclude optional service discoveries. See the Prometheus documentation for available build tags to customize which service discoveries are included.Summary
Target-allocator Changes
v0.144.0 to v0.145.0
Generated on: 2026-02-19 07:24:50
0.145.0
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.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.Summary