This repository was archived by the owner on Dec 9, 2022. It is now read-only.
GHA- ISO Private Ephemeral Runners in K8s with image per step #192
DrMerlin
announced in
Day One: GitHub on GitHub
Replies: 2 comments
-
|
@DrMerlin I was waiting for the "ephemeral" support, and didn't realize that is wasn't on par with an image per step. 😢 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thanks @DrMerlin - could you post this on the feedback repo so we can keep track of the request post-Universe? Thanks 🙏 Here's the public roadmap, which we'll update as we start work on features: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there- I was really hoping that GHA would announce parity for self-hosted/private runners - to allow the specification of a container image for any given step- just like public runners, and like other competing CI tools allow for with private runners.
This is the biggest limiting factor to deciding to use GHA at scale instead of other products at my company
I realize it would require a kubernetes scheduling operator- but it seems like it shouldn't be too hard to implement.
I have seen a few community approaches to fix this- but think this really needs first party support.
Is this on the road map anywhere?
The recent "ephemeral" and "webhook" changes are nice, I guess, but don't really move the needle for my company. We need image per step.
Beta Was this translation helpful? Give feedback.
All reactions