Remove containerStatsEnabled from values files
#3683
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
|
2.4? |
|
@chipzoller Not urgent, but 2.4 would be nice! It requires an associated Frontend change. https://kubecost.atlassian.net/browse/ENG-2887 |
|
This pull request has been marked as stale because it has been open for 90 days with no activity. Please remove the stale label or comment or this pull request will be closed in 5 days. |
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?
ContainerStats ETL files are not currently used by the product. Disable this feature on all agents to reduce the load incurred on Cost-model and Prometheus containers.
Does this PR rely on any other PRs?
Yes. An associated Frontend PR will be required to remove the following warning banner. The
QuantileOfMaxandQuantileOfAveragesalgorithms should be available for use out of the box with no additional configuration.How does this PR impact users? (This is the kind of thing that goes in release notes!)
Links to Issues or tickets this PR addresses or fixes
What risks are associated with merging this PR? What is required to fully test this PR?
TODO
How was this PR tested?
TODO
Have you made an update to documentation? If so, please provide the corresponding PR.
TODO