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

Selection between multiple external IPs should consider reachability #445

Open
FelixMcFelix opened this issue Jan 12, 2024 · 0 comments
Open
Labels
feature Planned and requested features
Milestone

Comments

@FelixMcFelix
Copy link
Collaborator

FelixMcFelix commented Jan 12, 2024

Currently, an instance having several floating IPs will choose one using only the hash of the flow-key (VPC-local IP, dst IP, proto, src port, dst port). This assumes that all IPs assigned to an instance are treated identically upstream for the purposes of routing and reachability of destinations.

Part of this is that different IP pools might encode different semantics to an end-user: Internet connectivity, internal-only IPs, or for exclusive VPN tunneling to a cloud host. We should be making use of routing table information to determine which IPs should be selected as a source for a given destination address.

@FelixMcFelix FelixMcFelix added the feature Planned and requested features label Jan 12, 2024
@FelixMcFelix FelixMcFelix added this to the MVP milestone Jan 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Planned and requested features
Projects
None yet
Development

No branches or pull requests

1 participant