-
Notifications
You must be signed in to change notification settings - Fork 419
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
block thanos agent upgrades and suggest fedetl #2998
Merged
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
jessegoodier
commented
Jan 27, 2024
thomasvn
approved these changes
Jan 29, 2024
Conflicts here. |
fixed |
/cherry-pick v2.0 |
jessegoodier
added a commit
that referenced
this pull request
Jan 29, 2024
ameijer
pushed a commit
that referenced
this pull request
Jan 31, 2024
…host-1141-yaml-actions * commit '9abf05499eab352d9a10590c282e8e9491939804': updated release note (#3027) Bumped image tag with tighter prediction interval (#3023) Bumped image tag with retry changes (#3021) Bump thanosio/thanos from v0.32.5 to v0.34.0 in /cost-analyzer (#3015) Bump grafana/grafana from 10.2.3 to 10.3.1 in /cost-analyzer (#3013) Bump prometheus/alertmanager from v0.25.0 to v0.26.0 in /cost-analyzer (#2914) Bump prometheus-operator/prometheus-config-reloader in /cost-analyzer (#3014) Fix 2.0 precondition for nightly environment (#3016) Enable forecasting by default, fix "early spike" forecast behavior (#3010) [GTM-199] take global annotations setting into etlutils (#3006) Update to check if saml is enabled, not just if the object exists. (#3005) block thanos agent upgrades and suggest fedetl (#2998) Move 2.0 precondition checks into a function (#2986)
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.
What does this PR change?
Blocking thanos agents until 2.x supports multi-cluster prometheus.
Does this PR rely on any other PRs?
No
How does this PR impact users? (This is the kind of thing that goes in release notes!)
Thanos based agents should remain on 1.x versions until 2.x supports multi-cluster prometheus.
What risks are associated with merging this PR? What is required to fully test this PR?
NA
How was this PR tested?
--set agent=true
Have you made an update to documentation? If so, please provide the corresponding PR.
Need to add statement in v2 doc.