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

As a developer I would like to be able to test my Openshift specific yaml inside GitHub actions using crc #16

Open
NissesSenap opened this issue Dec 11, 2020 · 8 comments

Comments

@NissesSenap
Copy link

Today there are github actions to start a kind cluster https://github.com/marketplace/actions/kind-kubernetes-in-docker-action as a github action.

Instead of starting a kind environment I would like to have openshift crc or something similar running inside a github action so I can test my open-source OCP specific yaml without having to have a OCP cluster running somewhere else.

@tetchel
Copy link
Contributor

tetchel commented Dec 14, 2020

We like this idea and will investigate it. I think it's likely we run into resource issues; CRC has high RAM and disk space requirements compared to kind or minikube.

@NissesSenap
Copy link
Author

Heared some unofficial talk about making crc to be able to run on 6 Gb memory and the GitHub actions runner provides 7Gb of memory. So might have to wait a bit to make it feasible.

I think one of the biggest issues is to make it start fast enough. But there might be some ninja ways that the crc team can help out to get some pre-loaded container images on it to save start time or something similar.

@tetchel
Copy link
Contributor

tetchel commented Dec 18, 2020

Hi @NissesSenap

Have you seen this action? https://github.com/manusa/actions-setup-openshift

@rtaniwa rtaniwa added this to Backlog in Sprint 199 Mar 25, 2021
@rtaniwa rtaniwa removed this from Backlog in Sprint 199 Apr 13, 2021
@rtaniwa rtaniwa added this to Backlog in Sprint 200 Apr 13, 2021
@rtaniwa rtaniwa removed this from Backlog in Sprint 200 May 6, 2021
@rtaniwa rtaniwa added this to Backlog in Sprint 201 May 6, 2021
@rtaniwa rtaniwa removed this from Backlog in Sprint 201 May 31, 2021
@rtaniwa rtaniwa added this to Backlog in Sprint 202 May 31, 2021
@rtaniwa rtaniwa removed this from Backlog in Sprint 202 Jun 14, 2021
@rtaniwa rtaniwa added this to To do in Sprint 203 via automation Jun 14, 2021
@rtaniwa rtaniwa moved this from To do to Backlog in Sprint 203 Jun 14, 2021
@rtaniwa rtaniwa removed this from Backlog in Sprint 203 Jul 6, 2021
@rtaniwa rtaniwa added this to Backlog in Sprint 204 Jul 6, 2021
@divyansh42 divyansh42 removed this from Backlog in Sprint 204 Aug 2, 2021
@divyansh42 divyansh42 added this to Backlog in Sprint 205 Aug 2, 2021
@rtaniwa rtaniwa removed this from Backlog in Sprint 205 Aug 23, 2021
@rtaniwa
Copy link

rtaniwa commented Sep 27, 2021

I am tempted to move this one as blocked. Do we really have many options here right now, or are we relying on CRC going down on their requirements before we can implement this on our side.

@tetchel
Copy link
Contributor

tetchel commented Sep 27, 2021

Yes, we need it to allow itself to run on 2 CPU and < 7GB RAM.

More like 6GB RAM because we have to leave some RAM to do other work.

https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources

@jduimovich
Copy link
Member

Lets update the doc to describe the requirements for this on a self-hosted runner.
I can run this on my desktop Windows 32G+, or Linux. The issue you just cannot run on Githubs runners so if we document this restriction and tell people how to do it could be enough for now until github runners get larger or CRC gets smaller

@rtaniwa
Copy link

rtaniwa commented Sep 27, 2021

We do have an issue to track that work already: #49

Given that, not sure this is even worth keeping open because afaik, there are no plans to make CRC small enough that it would ever work for running on GitHub infra.

@divyansh42 divyansh42 added this to To do in Sprint 212 via automation Jan 11, 2022
@divyansh42 divyansh42 moved this from To do to Blocked in Sprint 212 Jan 11, 2022
@divyansh42 divyansh42 removed this from Blocked in Sprint 212 Feb 3, 2022
@divyansh42 divyansh42 added this to To do in Sprint 214 via automation Feb 3, 2022
@divyansh42 divyansh42 moved this from To do to Blocked in Sprint 214 Feb 3, 2022
@divyansh42 divyansh42 removed this from Blocked in Sprint 214 Mar 1, 2022
@divyansh42 divyansh42 added this to To do in Sprint 215 via automation Mar 1, 2022
@divyansh42 divyansh42 moved this from To do to Blocked in Sprint 215 Mar 1, 2022
@divyansh42 divyansh42 removed this from Blocked in Sprint 215 Mar 16, 2022
@divyansh42 divyansh42 added this to To do in Sprint 220 via automation Jun 8, 2022
@divyansh42 divyansh42 moved this from To do to Backlog in Sprint 220 Jun 8, 2022
@divyansh42 divyansh42 moved this from Backlog to Blocked in Sprint 220 Jun 8, 2022
@divyansh42 divyansh42 removed this from Blocked in Sprint 220 Jul 8, 2022
@benjaminjb
Copy link

Hmmm, I wonder if MicroShift might be a good prospect for a GH action in the (hopefully) near future?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants