GitHub Runner Issues

[aba-d]

Select Topic Area

Question

Body

We have zero trust networks and using GitHub-hosted runners and GitHub Actions for CI/CD pipelines.
However, we are seeing the error "Curl: (6) could not resolve host: artifactory.xxx.net "

1. Following tools that are hosted in a private network and seeing the above error

• JFrog Artifactory
• SonarQube
• Veracode
• Prisma Cloud

Solution -
Could you please advise on recommended approaches or features (such as self-hosted runners, GitHub Enterprise, or hybrid solutions) that can help us overcome these challenges?

[herrksissoumarouane-glitch]

1. elf-hosted runners inside your private network**

   • Direct access to internal tools.
   • Your team is responsible for maintenance and security.

2. Hybrid approach**

• Use GitHub-hosted runners for public tasks, self-hosted runners for internal tasks.

3. GitHub Enterprise**

• Better management and scaling of self-hosted runners in private networks.

[yassine-krichen]

Yeah, that error basically confirms the problem: GitHub-hosted runners are out on the public internet, your tools are sitting behind a zero-trust wall, and the two will never see each other. Hosted runners just don’t get special networking magic.

Honestly, the only setup that actually works in these environments is:

• Self-hosted runners living inside your network.
They can hit Artifactory, SonarQube, Veracode, all of it, without fighting DNS or firewalls. It’s boring but it works.

• Or a hybrid setup.
Let GitHub-hosted runners do the public stuff, and use your own runners for anything behind the corporate bunker. Most companies end up here anyway.

• GitHub Enterprise helps with managing the runner farm if you have a lot of them, but it doesn’t change the physics: private tools require runners inside the private network.

If it makes you feel any better, everyone with a zero-trust setup hits this exact wall. Self-hosted is pretty much the only way out.

[aba-d]

Thank you @herrksissoumarouane-glitch and @yassine-krichen for the quick response. Currently we have GitHub Enterprise license and going to use (GitHub Actions, GHAS, Copilot, Codebases etc.)

What will be the best one in such scenario - Self-hosted runners living inside your network or hybrid setup?
Also, can you share some document where we can follow the process and get it setup.

Current org and repo structure.
GitHub Enterprise
Organization
Repo 1
Repo 2
Repo ...
Organization
Repo 1
Repo 2
Repo ...
Organization
Repo 1
Repo 2
Repo ...