We have a use-case when we want to run instances in DMZ or public subnet but without public ips. Elastic ip would be assigned later to one of the instances.
Without public ip instance will not be able to initialize (download docker, push logs, use AWS api, etc...). To solve this problem taupage will create separate routing table for outgoing https requests and use a custom nat gateway for that.
Coverage decreased (-0.1%) to 89.635% when pulling c5deae852ef7d7179a6d4da3572f99fa3a557d70 on CyberDem0n:feature/nat_gateways into 96c149e13fe296aa512510c3e2fdedd7b75365db on zalando-stups:master.
We have a use-case when we want to run instances in DMZ or public subnet but without public ips. Elastic ip would be assigned later to one of the instances. Without public ip instance will not be able to initialize (download docker, push logs, use AWS api, etc...). To solve this problem taupage will create separate routing table for outgoing https requests and use a custom nat gateway for that.