The issue was within the pod there was no route for the subnet outside VPC, but within AWS routing table associated with the subnet. Thus the pod had no idea how to route it and made a mess.
Maybe the better option would be to ask the AWS API for the subnet routing table and learn the needed routes from there, though this is a quick fix for my use case.
This solves #67
The issue was within the pod there was no route for the subnet outside VPC, but within AWS routing table associated with the subnet. Thus the pod had no idea how to route it and made a mess.
Maybe the better option would be to ask the AWS API for the subnet routing table and learn the needed routes from there, though this is a quick fix for my use case.