docs(scalers): Update cpu
and memory
scaler docs for validating requests
/limits
from LimitRange
#1296
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.
Provide a description of what has been changed
Update for cpu & memory scalers for KEDA controller checking for default limits and requests in LimitRange, for Container type, in the same namespace, for validation when the container resources are not specified in the pod spec.
Also, the following is updated:
When using
cpu
ormemory
scalers, the KEDA controller checks whetherrequests
orlimits
are specified for the container resources. Therequests
are specified in the docs, but thelimits
are missing. This change updates thecpu
andmemory
scaler docs to mention thelimits
that are also validated.Checklist
Relates to issue kedacore/keda#5348
Relates to PR kedacore/keda#5377