v0.10.0

Add/ignore cidr blocks @colinh6 (#43)

what

• This PR will introduce logic to ignore certain CIDR ranges from either the requestor or acceptor VPC(s), without affecting the existing functionality.

why

• We add the CIDR range 100.64.0.0/16 to each of our EKS cluster VPCs to increase the maximum amount of assignable IP addresses when using the AWS VPC CNI.
• This causes issues when attempting to leverage this existing peering module, as the 100.64.0.0/16 routes will conflict in certain cases.
• One specific case is where we want to peer and route a single database or elasticsearch VPC to multiple different EKS cluster VPCs that all contain the 100.64.0.0/16 additional CIDR association

references

• https://aws.amazon.com/premiumsupport/knowledge-center/eks-multiple-cidr-ranges/

git.io->cloudposse.tools update @dylanbannon (#38)

what and why

Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.

References

• DEV-143