improve: increase kyverno resource limits and add values#93
Merged
thesuperzapper merged 1 commit intoFeb 5, 2024
Merged
Conversation
Signed-off-by: Mathew Wicks <[email protected]>
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
1 participant
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.
This PR increases the default memory limit for the Kyverno background controller to
512Miand adds values to allow users to customize it further.This was necessary because our version of Kyverno (1.10.0, which we must use due to issues in newer versions, see #92), uses more memory when running deployKF than is allowed by its default configs.
The following values have been added:
deploykf_dependencies.kyverno.admissionController.resourcesdeploykf_dependencies.kyverno.backgroundController.resourcesdeploykf_dependencies.kyverno.cleanupController.resourcesdeploykf_dependencies.kyverno.reportsController.resources