fix(monitoring): fix thanos receive service stuck in Progressing on staging - #1645
Merged
davehadley merged 2 commits intoSep 24, 2026
Merged
Conversation
davehadley
marked this pull request as ready for review
September 23, 2026 14:35
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
2 participants
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.
Fixes issue on staging only where thanos-receive service was never reaching healthy state in ArgoCD
The LoadBalancer service never received an external IP, causing Argo CD to report it as Progressing indefinitely. Staging only requires internal access to Thanos Receive.
Switching to ClusterIP fixes this.