-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot set resources Requests and Limits for workflow pods #3641
Comments
Hey @jonathan-fileread, is there a way to configure this in the default values.yaml file provided with the gha-runner-scale-set charts? |
@kanakaraju17 Hey Kanaka, unfortunately not. you need to create a seperate podtemplate in order to define the workflow pod, as the values.yaml only defines the runner pod settings. |
@jonathan-fileread, any idea why the file is not getting mounted in the runner pods? I'm using the following configuration and encountering the error below:
ConfigMap Configuration
The pods fail and end up with the below error:
Have you tried recreating it in your environment? Have you come across this error before? It seems to be a mounting issue where the file is not found. |
@kanakaraju17 You can follow the official guide which worked for me at least :) In your case that would be something like: ConfigMap:
Usage:
|
Hey @georgblumenschein, Deploying the gha-runner-scale-set by adding the below env variables doesn't seem to reflect.
Additional ENV Variable Added:
The workflow pods should include the ACTIONS_RUNNER_CONTAINER_HOOK_TEMPLATE environment variable and volume mount but it doesn't appear when describing the pods. Currently, the output is missing this variable. Expected Result: Below are the values.yaml template used to append the environment variable:
Problem: Current Output: While Describing the AutoscalingRunnerSet doesn't show the ENV variables added either.
expected behavior: The ENV variable ACTIONS_RUNNER_CONTAINER_HOOK_TEMPLATE getting added along with the volume mounts along the pods which will come up. |
Checks
Controller Version
0.9.2
Deployment Method
Helm
Checks
To Reproduce
Describe the bug
The runner pods, which have names ending with "workflow," should have the specified resource requests and limits for CPU and memory when they are created.
Describe the expected behavior
The workflow pod that is created during the pipeline execution should have specific CPU and memory limits and requests set. However, it is not starting with the specified resources and limits.
Additionally, an extra pod is being created when the pipeline runs, alongside the existing runner pods. We need to understand the purpose of the existing runner pod if a new pod is also being initiated. Added the detail of the extra pod in the screenshot below.
Additional Context
Controller Logs
https://gist.github.com/kanakaraju17/31a15aa0a1b5a04fb7eaab6996c02d40 [this is not related to the resource request constraint for the runner pods]
Runner Pod Logs
The text was updated successfully, but these errors were encountered: