Multi-Region APIOps with Kong

Transcript

1. Multi-Region APIOps with Kong Kumar Abhijeet
2. 1 Agenda Multi-region API Gateways - 5Ws&H What’s APIOps? Kong and decK Multi-region woes and solutions!
6. 5 Challenges Manually configuring API Gateways No versioning, audits or access control Ops Dependency - No self serve Inconsistency across APIs Affects Delivery Speed and Quality
7. 6 Enter APIOps GitOps + DevOps for API/Microservices Lifecycle
9. 8 Why APIOps? Consistent & Standardized APIs Increased Dev Productivity & Delivery Audit Log and Version Control Better adoption of IDPs<>API Gateways Improved API Lifecycle Management
14. 13 Multi-Region Woes! API Equivalence across Regions Data Security Standards(PCI/SOC) No inter-region connectivity Managing multiple sources of truth Region-specific upstream endpoints
16. 15 1st Principles! One Env -> Multiple Clusters Single set of Kong configs within One Folder Clusters within same Env -> same Kong config One Env Folder -> One Env Tag based service<>cluster assignment
17. 16 GitOps Repo Structure
18. 17 Service Upstream
19. 18 Cluster Directory
20. 19 Tag based Segregation Upstream Generation
22. 11 Next Steps FOSSing the config generation/lint CI tooling Opinionated format as a standard Document more production experiences Atlantis-type PR automation tools