Gaining Flexibility with per-Route Features
summary
Proposal introduces a generic options map attached to route objects so operators or apps can set per-route load balancing and connection limits instead of global defaults. Implementation extends route-registrar to publish the map and updates Gorouter to parse and apply algorithms to backends; that path is working end-to-end for system routes. Next work touches BBS (DB migration), router-metadata and Cloud Controller changes; development discussion and contribution details live on implementation issue 9009.
AI-written summary · about
related talks
36mIngressRoute: A Path Towards a Better Ingress Object for Kubernetes
20mWhy File-based Routing Sucks and Why You Should Use It
27mIsolated Federated Schema Integration Testing with Router
22mN Things You Didn’t Know About the Router
38mRouting in Polaris
27mRouting and new features
29mHandle routes data using stateless protocol (using React Router)
45mRouting With Cofree Comonad