Repository navigation
Conversation
flake-ctl firecracker network init now supports the new option --egress-deny. The implementation adds a new chain FLAKE_PILOT_EGRESS. VM traffic to the outside world now jumps from FLAKE_PILOT_FORWARD into the new chain. The new chain holds the egress drop rules first. For two prominent restrictions the --egress-deny option was simplified: * --egress-deny link-local * --egress-deny private link-local blocks 169.254.0.0/16, which includes the cloud metadata service at 169.254.169.254. Without it, a VM reaches that service as the host and can read the instance's credentials. private blocks the RFC 1918 ranges: 10/8, 172.16/12 and 192.168/16. The policy is IPv4 only like the rest of the setup
This branch has not been deployed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
flake-ctl firecracker network init now supports the new option --egress-deny. The implementation adds a new chain FLAKE_PILOT_EGRESS. VM traffic to the outside world now jumps from FLAKE_PILOT_FORWARD into the new chain. The new chain holds the egress drop rules first. For two prominent restrictions the --egress-deny option was simplified:
link-local blocks 169.254.0.0/16, which includes the cloud metadata service at 169.254.169.254. Without it, a VM reaches that service as the host and can read the instance's credentials. private blocks the RFC 1918 ranges: 10/8, 172.16/12 and 192.168/16.
The policy is IPv4 only like the rest of the setup