Enable the VerticalPodAutoscalerCappedRecommendation alerts
#11622
Conversation
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
This is achieved by setting the alert severity and topology.
Closed
3 tasks
|
LGTM label has been added. Git tree hash: 75a8ee06fbec913a58f46c0332733fa1203c4d8f
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: istvanballok, ScheererJ The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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.
How to categorize this PR?
/area monitoring
/kind enhancement
What this PR does / why we need it:
#11136 introduces a new
VerticalPodAutoscalerCappedRecommendationalert when a VPA uncapped target recommendation is larger than the regular target. #11325 revisits this to address a few caveats with the original alert that went undetected in development environments. In both cases, however, the alert was never enabled. Initially, we wanted to introduce the alert without enabling it to develop an understanding of its behaviour, such as how often it would fire. Now, in this PR, we proceed to enable it.Special notes for your reviewer:
/cc @istvanballok @rickardsjp @chrkl
Release note: