Open FabianKramm opened 2 years ago
Me and @pratikjagrut discussed a possible refactor of GH actions. Proposed new setup:
I don't know if we should use the same repo as we have for release builds. - @FabianKramm what do you think? If not, then I would personally use quay.io for hosting images. It doesn't have unauthorized pull restrictions which are present in docker hub. Also, it is possible to set expiration time - automatic deletion of an image after a certain time.
Thanks for the update @matskiv ! Regarding your ideas:
We can have a separate package such as ghcr.io/loft-sh/vcluster-dev for PR builds while ghcr.io/loft-sh/vcluster for release builds.
@FabianKramm We would have an automated clean-up job that will trigger on PR merge. A separate ghcr.io/loft-sh/vcluster-dev package sounds good to me.
There are a few more tests remaining from the description. I think we should keep it open.
Currently we deploy vcluster in a single configuration in parallel in 4 different jobs for each distro. While this works and smoke tests vcluster, several features and areas of vcluster remain untested due to this single deployment of vcluster. Hence I propose to deploy vcluster within those jobs multiple times in different configurations, so that we can test certain features as well.
Currently untested vcluster functionality (might be incomplete):