Cannot set resource requirements for fs-init container in k8s-novolume mode

[TonyNoble]

When using a containerMode of 'kubernetes-novolume', the k8s-novolume hook script creates an init container called 'fs-init'. It is not currently possible to set the resource requests and limits for this container, which breaks deployment on infrastructures that require them to be declared.

Additionally it does not appear to be practical to override the entire 'fs-init' init container as its definition is conditional.

Ideally, it would be possible to override similar to the job container - by merging pod template definitions

[nikola-jokic]

Hey,

Have you tried using hook extension?

https://github.com/actions/runner-container-hooks/blob/main/docs/adrs/0134-hook-extensions.md

[nikola-jokic]

Closing this issue now since the hook extension was intended way of allowing users to specify and modify the spec without having to rebuild the hook. The experimental charts now contain the hook extension config out of the box in ARC.

[TonyNoble]

@nikola-jokic - Please re-open - this is specifically an issue with the hook extensions.

It does not appear to be possible to use the extensions to modify the the resource requirements of the fs-init initContainer auto-generated by the hook script.