Parameterise Trident Operator k8s resources #997
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.
Change description
We've observed CPU throttling happening to the trident-operator pod with the hardcoded CPU/MEM resources. Hence I've moved the harcoded resources to the default values , which will allow parameterisation of the resoures in case someone wants to.
Project tracking
N/A
Do any added TODOs have an issue in the backlog?
N/A
Did you add unit tests? Why not?
N/A
Does this code need functional testing?
N/A
Is a code review walkthrough needed? why or why not?
Yes, but as I'm an external developer, not sure who I'd ask
Should additional test coverage be executed in addition to pre-merge?
Don't think so as helm templates fine
Does this code need a note in the changelog?
No
Does this code require documentation changes?
No
Additional Information