feat: allow setting gitlab-runner instance egress rules #257
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ab_runner_egress_rules
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Currently, the module allows all egress traffic from the gitlab-runner instance. From a security point of view, I might want to limit the egress network connectivity from the gitlab-runner instance. This PR introduces a new variable called
gitlab_runner_egress_rulesthat allows the user of this module to configure additional egress rules.Migrations required
NO, however the new default egress rule for the gitlab-runner now also allows egress traffic to all IPv6 address.
Documentation
✔️