Gitlab runner migration and resource limit expansion

Infrastructure as Code & Cloud Native
, , ,
1

Replace this template with your information

Describe your question in as much detail as possible:

The documentations Advanced configuration | GitLab and Runners autoscale configuration | GitLab and The Kubernetes executor | GitLab are very confusing on how much Gitlab Runner pods would consume from K8S for jobs, I need help with expanding their limits because I have a feeling that the RSS they use to build, test, release is quiet too low which can be a reason of long running jobs.

The closest documentation that I found is The Kubernetes executor | GitLab but I have zero idea where config.toml is. Also I see that those are not aligned with Cluster Management Project Template | GitLab.

Can someone please help?

Furthermore, I am trying to migrate from helm 2 to helm 3 as advised in Migrate from GitLab Managed Apps to Cluster Management Projects | GitLab but I am not able to, do anyone have an automated shell/ps script to help with this please?

  • What are you seeing, and how does that differ from what you expect to see?

  • Consider including screenshots, error messages, and/or other helpful visuals

  • What version are you on? Are you using self-managed or GitLab.com?

    • GitLab (Hint: /help): 14.0.5
    • Runner (Hint: /admin/runners):

  • Add the CI configuration from .gitlab-ci.yml and other configuration if relevant (e.g. docker-compose.yml)

  • What troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?
    I have did and still doing a tons of research, I’ve been more than a month working on it. It’s very painful.

Thanks for taking the time to be thorough in your request, it really helps! :blush: