- TCP Routers are now automatically updated by creating/updating/deleting LRPs via Diego. The routers fetch their configuration from Routing API; TCP emitter watches Diego and populates Routing API epic
- Routing components are highly available and horizontally scalable (in progress) epic
Misc
- Creating a tcp route requires a router group guid; if diego client specifies a router group guid with tcp route, tcp-emitter will send it to the routing api details
- Operator can now disable the requirement for authentication on the routing api; components will not attempt to contact uaa details
- When updating an LRP, requests are no longer routed to the backends removed from a route details
- routing API can be use to delete one or more tcp route mappings details
- When deleting an LRP with a tcp routes, backends are no longer accessible by the route details