Since all the IPs from a subnet reside on the same node in our k8s deployment, route aggregation will ensure minimal configuration update during pod bring up.

• Instead of /32 prefixes in FIB (as of today), the entries contain a subnet route whose next hop is the node to which that subnet is assigned
• When a pod is brought up on a node, ODL will only update the FIB on that node to handle packets destined to the pod.
• Note: Route Aggregation is NOT present in ODL today, since it does not make sense in the NFVi deployment model. Route aggregation must be added to ODL