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

GitHub Actions: use "larger" runners for nested virt #3364

Closed
AkihiroSuda opened this issue Sep 18, 2023 · 4 comments
Closed

GitHub Actions: use "larger" runners for nested virt #3364

AkihiroSuda opened this issue Sep 18, 2023 · 4 comments

Comments

@AkihiroSuda
Copy link
Member

AkihiroSuda commented Sep 18, 2023

name: Cgroup v2
# nested virtualization is only available on macOS hosts
runs-on: macos-12

The current CI uses very slow macos-12 instances for nested virtualization, but the CI can get better performance and stability by switching it to "larger" Linux runners such as ubuntu-latest-4-cores: https://github.blog/changelog/2022-10-20-github-actions-larger-hosted-runners-are-now-automatically-created-for-customers/

CNCF projects have accesses to larger instances, but it has to be explicitly enabled by an admin of https://github.com/kubernetes-sigs :

@AkihiroSuda
Copy link
Member Author

(For cgroup v2, we can just consider switching from the Fedora VM to the free ubuntu-22.04 instances, but having a test with Fedora VM still makes sense, as its LSM and root filesystem is different from Ubuntu)

@BenTheElder
Copy link
Member

Thanks!
We'll have to make a request with https://github.com/kubernetes/org

@AkihiroSuda
Copy link
Member Author

Thanks! We'll have to make a request with https://github.com/kubernetes/org

Thanks, made a request:

@AkihiroSuda
Copy link
Member Author

Standard runners now support nested virt:

@AkihiroSuda AkihiroSuda closed this as not planned Won't fix, can't repro, duplicate, stale Jan 19, 2024
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

Successfully merging a pull request may close this issue.

2 participants