BGP Fabric) Protocol Reduction (No-Overlay) No Overlay Network Service We Get Simple & High Capacity Issues No Managed Network policy Public-IP High Consumption We need gateway solution !
Active L2 Network L2 Network Miss-match with Full L3 Network NG#3 Mechanism needs (1) N+1 Active/Active Single Cluster (2) Full L3 Simple Network Aware Let’s Construct the New One
with Many Stateless Active path • 2nd step: Not Robust but Blast Radius is 1/N • Gracefull v.s. Small Blast Radius • “Small Blast Radius and Hyperscale” >>> "Big Blast Radius and Graceful” • Getting Gracefully is Additional-Step
• With • Declarative Configuration • Resource-Watch • Reconciliation • Use CloudNative Parts • Use Consul for dataplane clustering • Use Etcd as Watchable Robust KVS Respecting K8s
• With • Declarative Configuration • Resource-Watch • Reconciliation • Use CloudNative Parts • Use Consul for dataplane clustering • Use Etcd as Watchable Robust KVS Offload Complex Mechanism
software → Really Really Difficult • reboot-able software → More Easy and Realistic • Basic Principle • Casual Maintenance • Frequency Upgrade Enabled by Declarative Model and Reconciliation loop
new routing mechanism called “FabricNAT” for backend • Distributed NAT mech achieving “Small Blast Radius” and “Hyperscale” • SDN Design using CloudNative blocks • Consul for Easy/Massive clustering • Etcd for Declarative Configuration • Stateless software component can be restart casually • Many Network Challenge on our Private Cloud :)