-
Notifications
You must be signed in to change notification settings - Fork 48
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
Possibility to specify resources and limits for services containers #132
Comments
Hey @katarzynainit, I think the best approach is to follow the |
Understood! |
I can take this one, unless you would like to contribute |
Will ping you with PR once it's ready :) |
…rs (#134) #132 Co-authored-by: Katarzyna Radkowska <[email protected]>
Related to actions#132
Hi @nikola-jokic |
Hi @katarzynainit, Or would this be part of an additional implementation phase @nikola-jokic ? |
Hey @katarzynainit, I'm sorry for the delay. I hope I'll review these changes this week, and we can issue a new hook release for them Thank you again for your contributions! @David9902 With the current change, no, but there could be a way of having |
Thanks for merging the PR :) I'm leaving the issue open as there is additional discussion with @David9902 |
Hi,
I'm using ARC with runner-container-hooks in
kubernetes
mode.I'd like to be able to define resources/limits for the services.
When service container is added to the container job pod, it has no resources defined, which, in my case, is not accepted (I need to provide some resources, otherwise I will get default values, which are way to small to operate).
Currently, the only way to do it, is to use ACTIONS_RUNNER_CONTAINER_HOOK_TEMPLATE providing services as fixed containers in the spec, which means I cannot use them from workflow - I will end up with containers with names that are duplicated (from service and from pod spec).
Am I missing something?
Would it be possible to either provide resources from workflow, or to follow $job pattern (from the hook) to only adjust service containers?
The text was updated successfully, but these errors were encountered: