Skip to content

Overwrite kubernetes resource limits and requests for build container on job level

Nicholas Colbert requested to merge Ticketmaster/gitlab-runner:kubernetes_pod_resources_override into master

What does this MR do?

When using the Kubernetes executor this allows the predefined cpu and memory allocations for builds to be overwritten up to a predefined max.

Why was this MR needed?

We have use cases where the predefined cpu and memory resources do not meet the needs of the user.

Does this MR meet the acceptance criteria?

  • Documentation created/updated
  • Tests
    • Added for this feature/bug
    • All builds are passing
  • Branch has no merge conflicts with master (if you do - rebase it please)

What are the relevant issue numbers?

Related to #2902 (closed), #4673 (closed)

Edited by Tomasz Maczukin

Merge request reports