You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the unset-cpu-requirements requires requests and limits while in general having only requests should be sufficient. Requests are essential for scheduling, and since omitting limits would simply allow the application to utilize a slightly higher amount of CPU if necessary, we should no longer recommend specifying both requests and limits.
Currently the
unset-cpu-requirements
requires requests and limits while in general having only requests should be sufficient. Requests are essential for scheduling, and since omitting limits would simply allow the application to utilize a slightly higher amount of CPU if necessary, we should no longer recommend specifying both requests and limits.The change should happen in check definition
kube-linter/pkg/builtinchecks/yamls/unset-cpu-requirements.yaml
Line 11 in e68f7d1
As well in related tests:
@test "unset-cpu-requirements" {
kube-linter/e2etests/bats-tests.sh
Line 895 in e68f7d1
The text was updated successfully, but these errors were encountered: