You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The problem is that the over-allocation check is incredibly subjective, since it seems to just grab the current metric for each service. If you want to sanity test a cluster that may have absolutely no load on it, you will always get piles of warnings that are for the most part meaningless. In a sanity test of a cluster's configuration, in some cases you only care about under-allocated as your request/limits are set for real production values.
Describe the solution you'd like
A way to disable the over-allocation test, tried playing with the values and couldn't get it to just go away.
Describe alternatives you've considered
None
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
@jclarksnps Thank you for this report! I agree over-allocation warnings yields false positive when the cluster is not under heavy load. I will add an option to silence these in the next drop.
Is your feature request related to a problem? Please describe.
The problem is that the over-allocation check is incredibly subjective, since it seems to just grab the current metric for each service. If you want to sanity test a cluster that may have absolutely no load on it, you will always get piles of warnings that are for the most part meaningless. In a sanity test of a cluster's configuration, in some cases you only care about under-allocated as your request/limits are set for real production values.
Describe the solution you'd like
A way to disable the over-allocation test, tried playing with the values and couldn't get it to just go away.
Describe alternatives you've considered
None
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: