fix(zarf): Relax the default resource limits & request variables #17
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
As a template, we should not be perscribing a default limit to the CPU and Memory allocations of deployments. This should be handled by the zarf configurations that import this skeleton.
justinthelaw
approved these changes
Mar 6, 2024
gphorvath
approved these changes
Mar 8, 2024
CollectiveUnicorn
approved these changes
Mar 8, 2024
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.
As a template, we should not be prescribing a default limit to the CPU and Memory allocations of deployments. This should be handled by the Zarf configurations that import this skeleton.
By having restrictive defaults, applications using this skeleton could unknowingly self-hinder themselves by not giving it enough resources to perform inference.