cpu and memory Requests are not configurable for any services

[michaelfedell]

The Community and Enterprise helm charts do not provide a way to configure CPU or Memory Requests. Limits are configurable, but without configurable Requests, the kubernetes scheduler can force these pods into a relatively small space leftover on any given node, leading to undesirable throttling.

A much more flexible option might be to take the fairly standard approach of letting a user directly pass in the entire resources block for a workload.

Example:
Hard-coded in the Plane helm charts for each workload
https://github.com/makeplane/helm-charts/blob/develop/charts/plane-ce/templates/workloads/worker.deployment.yaml#L27-L28

E.g. aws-load-balancer-controller helm chart allows for setting entire resource block
Values: https://github.com/aws/eks-charts/blob/master/stable/aws-load-balancer-controller/values.yaml#L62-L72
Workload: https://github.com/aws/eks-charts/blob/master/stable/aws-load-balancer-controller/templates/deployment.yaml#L229-L230

This same pattern can be seen in the starter chart produced by helm create ...

[akshat5302]

This issue has been resolved in this PR#118