This website uses cookies to ensure you get the best experience.
Learn more.
A deployment must reach an internal endpoint through a controlled network path. Standard GitHub-hosted runner addresses change, and the organization does not want a very broad IP allow list. Which architecture is most suitable?
Published
- Limit the workflow to the default branch but leave network routing and endpoint access unchanged.
- Store the internal endpoint in a repository variable and assume this creates a private route.
- Keep standard hosted runners and treat one observed address as permanently assigned.
- Place deployment on a restricted runner group with controlled egress and authorize only repositories that need that network access.
Comments — 0
Sign in to comment