no-resource-limits-pods rule uses limit instead of limits

[mleneveut]

Describe the bug

The no-resource-limits-pods rule uses container.resources.limit instead of container.resources.limits

To Reproduce

Steps to reproduce the behavior:

1. Go to 'Rule Editor'
2. Click on 'no-resource-limits-pods' rule
3. Go to 'Rule script' tab
4. See error

Environment Details:

• Kubernetes Distribution/Version [e.g. GKE v1.13.12-gke.25, OpenShift 4.3] AKS v1.19.3
• Browser [e.g. chrome, safari] Chrome
• Version [e.g. v0.3] 0.8.15

[rubenhak]

@mleneveut, ah, a typo. Thanks for posting! :)

[rubenhak]

@mleneveut, fixed in version 0.9.9. Unfortunately since that is a default rule, upgrade over existing deployments wouldn't fix the rule. Any new deployments would have the correct rule. Thanks for submitting the issue.

helm upgrade --atomic -i kubevious kubevious/kubevious --version 0.9.9 -n kubevious