Home Explore Blog CI



kubernetes

4th chunk of `content/en/blog/_posts/2017-08-00-High-Performance-Networking-With-Ec2.md`
9e31fdcd702e759ea818ed4ac18afc7ed61bc79d41b75d9a0000000100000455
The latest release of Romana also addresses questions about how VPC routes are installed; what happens when a node that is forwarding traffic fails; how forwarding node failures are detected; and how routes get updated and the cluster recovers.


Romana v2.0 includes a new AWS route configuration function to set VPC routes. This is part of a new set of network advertising features that automate route configuration in L3 networks. Romana v2.0 includes topology-aware IP address management (IPAM) that enables VPC route aggregation to stay within the 50 route limit as described here, as well as new health checks to update VPC routes when a routing instance fails. For smaller clusters, Romana configures VPC routes as kubenet does, with a route to each instance, taking advantage of every available VPC route.


## Native VPC Networking Everywhere


When using Romana v2.0, native VPC networking is now available for clusters of any size, with or without network policies and for HA production deployment split across multiple zones.




Title: Romana v2.0 Enables Native VPC Networking Everywhere
Summary
Romana v2.0 addresses VPC route installation, node failure handling, and route updates. It includes an AWS route configuration function and topology-aware IPAM for VPC route aggregation. Health checks update VPC routes when a routing instance fails. For smaller clusters, Romana configures VPC routes like kubenet. Romana v2.0 enables native VPC networking for clusters of any size, with or without network policies, and for HA production deployments across multiple zones. The image shows Native VPC networking availability, noting it's available in Single and Multi zone setups when using Romana v2.0