Skip to content
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

Open
katarzynainit opened this issue Feb 9, 2024 · 8 comments
Open
Labels
enhancement New feature or request k8s

Comments

@katarzynainit
Copy link
Contributor

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?

@nikola-jokic nikola-jokic added enhancement New feature or request k8s labels Feb 12, 2024
@nikola-jokic
Copy link
Contributor

Hey @katarzynainit,

I think the best approach is to follow the $job pattern and re-use it for services. This would be a good improvement of the hook extension for sure.

@katarzynainit
Copy link
Contributor Author

Understood!
Any possibility to see such option on the "backlog"? Or you'd rather expect contribution? :)

@nikola-jokic
Copy link
Contributor

I can take this one, unless you would like to contribute ☺️ I can review it

@katarzynainit
Copy link
Contributor Author

Will ping you with PR once it's ready :)

katarzynainit pushed a commit to katarzynainit/runner-container-hooks that referenced this issue Feb 12, 2024
katarzynainit pushed a commit to katarzynainit/runner-container-hooks that referenced this issue Feb 12, 2024
katarzynainit pushed a commit to katarzynainit/runner-container-hooks that referenced this issue Feb 12, 2024
nikola-jokic pushed a commit that referenced this issue Feb 20, 2024
…rs (#134)

#132

Co-authored-by: Katarzyna Radkowska <katarzyna.radkowska@sabre.com>
katarzynainit added a commit to katarzynainit/runner-container-hooks that referenced this issue Feb 26, 2024
@katarzynainit
Copy link
Contributor Author

Hi @nikola-jokic
Can you please check #136 ?

@David9902
Copy link

Hi @katarzynainit,
thanks that you brought up this topic!
What I am wondering here actions/actions-runner-controller#3338 is it possible to set just one spec for all service containers?

Or would this be part of an additional implementation phase @nikola-jokic ?

@nikola-jokic
Copy link
Contributor

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 $service as container to specify it. I'll reach out to the team to get a second opinion, and I'll let you know 😄

nikola-jokic pushed a commit that referenced this issue Mar 14, 2024
@katarzynainit
Copy link
Contributor Author

Thanks for merging the PR :)

I'm leaving the issue open as there is additional discussion with @David9902

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request k8s
Projects
None yet
Development

No branches or pull requests

3 participants