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

Replace self-hosted CI runners with GitHub-hosted ones #156

Open
qdeslandes opened this issue Nov 5, 2024 · 0 comments
Open

Replace self-hosted CI runners with GitHub-hosted ones #156

qdeslandes opened this issue Nov 5, 2024 · 0 comments

Comments

@qdeslandes
Copy link
Contributor

qdeslandes commented Nov 5, 2024

The CI uses self-hosted runners because when the CI workflow was created, GitHub-hosted runner didn't comply with the following requirements:

  • Run on Linux 6.4+: only Ubuntu 22.04 was available, running on an old Linux kernel.
  • Support arm64 runners: while GitHub has provided arm64 runners for some time now, they run on Apple Silicon, which doesn't allow for nested virtualization, thus preventing Docker from being used.

Lately, GitHub fixed both of those blockers as it provides arm64 runners on Ubuntu 24.04 for Team and Enterprise Cloud plans, which makes those available to bpfilter through the Facebook org.

Self-hosted runners come with some maintenance that we should avoid if we can, and bpfilter's CI should be modified to use the GitHub runners instead of the self-hosted ones.

Tests have been conducted to validate the viability of the self-hosted runners, especially when it comes to the usage of BPF_PROG_TEST_RUN (see better_ci branch). To benefit from the arm64 Ubuntu runners, the development, and tests must be performed on the main repository, meaning people without writing rights can't contribute to this task.

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

No branches or pull requests

1 participant