cpulimit | CPULimit Patch for VM 's CPU resource control

If you want to be sure your pod/deployment won't consume more than 1.0Gi of memory then setting that MemoryLimit will do job just fine.

Once you set that limits and your container exceed it it becomes a potential candidate for termination. If it continues to consume memory beyond its limit, the Container will be terminated. If a terminated Container can be restarted, kubelet restarts it, as with any other type of runtime container failure.

For more readying please visit section exceeding a container's memory limit

Moving on if you wish to scale your deployment based on requests you would require to have custom metrics to be provided by external adapter such as prometheus. Horizontal pod autoascaler natively provides you scaling based only on CPU and Memory (based on the metrics from metrics server).

The adapter documents provides you walkthrough how to configure it with Kubernetes API and HPA. The list of other adapters can be found here.

Then you can scale your deployment based on the http_requests metric as showed here or request-per-seconds as described here.

You have to customize your docker image to work in the sidecar container. As an example you can take a look at images which are already used in Che in sidecars: https://github.com/eclipse/che-plugin-registry/blob/master/CONTRIBUTE.md#sidecars

Try to create next structure:

Instead of using the "cg tools", I would do it the "hard way" with the shell commands to create the cpulimit cgroup (it is a mkdir), set the cfs parameters (with echo command in the corresponding cpu.cfs_* files), create a sub-shell with the (...) notation, move it into the cgroup (echo command of its pid into the tasks file of the cgroup) and execute the requested command in this subshell.

Hence, cgrun.sh would look like this:

You can find this informations in gitlab documentation.

Enabling RBAC support

If your cluster has RBAC enabled, you can choose to either have the chart create its own service account or provide one on your own.

To have the chart create the service account for you, set rbac.create to true:

Your use of {{- range .Values.workers }} and {{- if .autoscaling.enabled }} is fine. You are not getting any values because .minReplicas, .maxReplicas, etc, are inside .autoscaling scope.

See Modifying scope using with

Adding {{- with .autoscaling}} will solve the issue.

Extending my last comment, I suppose that TAG_NUMBER variable is somewhere in your CI Gitlab job. However, you are not able to be authorized with the assigned variables in --docker-username and --docker-password docker flags. Have you checked the credentials used for the connection to docker-registry? Or it might be the option to manage secret within a GitLab Runner Helm Chart template.

Memory limits for processes in Linux usually go like this:

1. You set a memory limit for your current process via the setrlimit system call (man page)
2. Run the process who's memory you want to limit. The child will inherit the parent's limit upon creation.
3. Viola! You are now running the child process with the memory limit set to your liking.
4. Reset the parent's memory limit (which won't effect the child!)

In practice, that looks like this:

In helm templates this is done via pipelines. Some of them are defined via Go template language and some others are part of Sprig template library.

I did not find a complete list which are valid and working in Helm, but I did not find a Sprig one not working as explained in the Sprig documentation.

So first the syntax for pipelines has to be:

Using a queue is the way to go. A simple solution that I use is Task Spooler. You can limit the number of cores ffmpeg uses with -threads also. Here's some code for you: