fix(ScaledObject): Check default limits from LimitRange for ScaledObject validations
#5377
Task list completed / task-list-completed
succeeded
Jan 18, 2024 in 0s
6 / 6 tasks completed
All tasks have been completed
Details
Required Tasks
| Task | Status |
|---|---|
| I have verified that my change is according to the deprecations & breaking changes policy | Completed |
| Tests have been added | Completed |
| Changelog has been updated and is aligned with our changelog requirements | Completed |
| A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified) kedacore/charts#588 | Completed |
| A PR is opened to update the documentation on (repo) (if applicable) kedacore/keda-docs#1296 | Completed |
| Commits are signed with Developer Certificate of Origin (DCO - learn more) | Completed |
| Deploy from the current branch. | Incomplete |
| Run test scripts from [keda-5348.zip][1]. | |
Only no-default-cpu-memory-limits.sh should throw the below-mentioned error, and no error for default-limits-in-limitrange.sh. |
Incomplete |
Loading