Allow native resource request/limit for containers
Hi! I've been trying to use this helm to setup a build service in a Kubernetes cluster on bare metal, and in its current stage is completely impossible to do so.
Right now, if I want to define limits for any of the containers involved in a job, I have to use a weird syntax only followed by gitlab's helm chart: cpuLimit, cpuRequest...
Could it be possible to define container limits using kubernetes' standard resource declaration?
Defining resources using the standard syntax will also allow to define other resource needs, like the new
hugepages, which have been a great improvement on resource management for kubernetes clusters.
In general, I find this helm chart unusable due its constant rewriting of kubernetes syntax. There are too many lacking features that will be there if instead of rewriting kubernetes API it was just exposing placeholders for them.
I'm finding the same problems in other parts, like extra volume declarations or configmap support for mounting files.