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-memory-requirements requires both requests and limits. This is redundant as request if not set will be copied from limits. The memory differs from CPU as with not enough CPU the container will slow down while with missing memory it will be killed. That's why requirements and limits should be set to same value.
The change should happen in check template definition
Currently the
unset-memory-requirements
requires both requests and limits. This is redundant as request if not set will be copied from limits. The memory differs from CPU as with not enough CPU the container will slow down while with missing memory it will be killed. That's why requirements and limits should be set to same value.The change should happen in check template definition
requirementsType: "any"
@test "unset-memory-requirements" {
kube-linter/pkg/builtinchecks/yamls/unset-memory-requirements.yaml
Line 11 in 24d1fe3
As well as in the related tests:
kube-linter/e2etests/bats-tests.sh
Line 916 in e68f7d1
The text was updated successfully, but these errors were encountered: