Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • gitlab-runner gitlab-runner
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 3,459
    • Issues 3,459
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 109
    • Merge requests 109
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • gitlab-runnergitlab-runner
  • Issues
  • #28098
Closed
Open
Issue created Jul 28, 2021 by Ustuzhanin Anton@toshaust

Kubernetes executor failed quota: quota-limit: must specify limits.cpu,limits.memory,requests.cpu,request

Summary

kubernetes executor runners pod not started with error message:

ERROR: Job failed (system failure): prepare environment: setting up build pod: pods "runner-zwnhlm8-project-821-concurrent-0md2jl" is forbidden: failed quota: quota-limit: must specify limits.cpu,limits.memory,requests.cpu,requests.memory. Check https://docs.gitlab.com/runner/shells/index.html#shell-profile-loading for more information

Steps to reproduce

Add quota to runners namespace. Try start job

Actual behavior

Init-container with name init-logs not have resources.cpu and resources.memory

Expected behavior

Add in config analogue of helper_cpu_request, helper_cpu_limit ... etc for init-logs

Environment description

Kubernetes executor

Used GitLab Runner version

Running with gitlab-runner:alpine-v14.1.0

Assignee
Assign to
Time tracking