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?
Hi,
I'm using ARC with runner-container-hooks in
kubernetesmode.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?