updated turbo profile controller to handle data.resource #2287
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.
Currently limited to setting
.spec.services[].resources.data.resources.limits.cpu
to{}
value instead of entirelimits
field because some internal functionality is removing the{}
value for entirelimits
field.The code as-is will work regardless because when one of the k8s resources fields gets set to
{}
, then ODLM will ignore sizing.How to test
profileController: turbo
cpu: {}
for the EDB and Keycloak CRs