Should there be a default CPU/Memory limits for the function deployments?

[murali-reddy]

Is this a BUG REPORT or FEATURE REQUEST?:

Feature request.

What happened:

Opening an issue as follow up to the discussion in #606. By default deployment used for function has no upper limit of CPU and memory. It would be ideal to put uppercap on the resources?

This should prevent rogue function to hog memory resources for e.g. which eventually may leading node not available.

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Kubernetes version (use kubectl version):
• Kubeless version (use kubeless version):
• Cloud provider or physical cluster:

[murali-reddy]

https://docs.aws.amazon.com/lambda/latest/dg/limits.html

[sayanh]

@murali-reddy Additionally IMO, default and configurable CPU/memory limits for init containers are also required.