Cherry pick changes for 1.5.1 #2207
Merged
Conversation
This file contains 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
* Fixed an issue in the `otlp.exporter.prometheus` component * Fixed an issue in the `otlp.exporter.prometheus` component
* Fix potential deadlock in import statements * change * typo
* Refactor ui remtoecfg components to avoid race condition * Fix accidental cast to pointer that should have been struct * Update changelog
* Fully prevent panic in remotecfg ui * Address PR feedback
* Fix deadlock due to infinite retry * changelog
* Upgrade ckit and changelog * go mod tidy
…nally. (#2187) * Fix issue which disables clustering unintentionally.
* prometheus.operator.*: allow setting informer_sync_timeout * default to 1m * docs
#2190) * Only take into account some labels * Reword docs
* fix: crash when updating import.http config
* Update postgres exporter * Update changelog * Use postgres exporter branch that implements exporter package * Add TODO for future maintainers
* Fix pyroscope.write issues with pyroscope.receive_http The nodejs Pyroscope SDK sends profiles with a `Connection: close` header. This header was copied to the upstream request, causing connection churn towards Pyroscope, which can be quite bad on the CPU when using TLS. Do not copy the `Connection` header from the incoming request to fix this issue. Additionally, `pyroscope.write` had a single `http.Client` used for forwarding data from `pyroscope.receive_http`, which may not work if multiple endpoints are configured with different options. To fix this, store a `http.Client` for each endpoint.
Merged
thampiotr
approved these changes
Dec 3, 2024
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.
Preparing for 1.5.1 by updating the VERSION file and cherry picking these commits:
dc9ec03
c99137c
e19c783
3bc6bfe
a319983
e61ad14
5d47b91
d82f44b
2b16ff0
45ef571
9177f33
1ba29ea
395e8cd
94dd6f2
@mattdurham unfortunately, it was difficult to cherry pick a37e481 and a914fd2 with remote queue changes.