Cross-regions service mesh by Traffic Director

// 如何透過 Traffic Director 來實現跨區域服務網格
透過 Service Mesh 的部署，在單一叢集我們能輕易地將微服務 Business Logic 與網路連線需求進行分離。但是服務網格面對單區域多叢集、VMs/K8s集成環境甚至是跨區域全球部署的需求，我們該如何實現呢？本次分享將介紹 Traffic Director 所提供的功能及透過 demo 來介紹實作的細節。

Transcript

1. Cross-regions service mesh by Traffic Director Astley Chen GDG Cloud Taipei co-organizer, Cloud Solution Architect
2. DevOps Engineer Cloud Solution Architect BI Data Engineer Astley Chen GDG Cloud Taipei Co-Organizer Docker, Docker Compose Kubernetes Service Mesh
3. 1. What is Service Mesh 2. What is Traffic Director 3. Use Cases 4. Demo 5. References Outlines
4. From Monolith to Microservices https://blog.knoldus.com/why-do-you-always-choose-microservices-over-me-said-the-monolithic-architecture/ Advantages: • Easier to scale • Rapid build/test/release cycles • Clear ownership and accountability
5. From Monolith to Microservices https://hackernoon.com/microservices-are-hard-an-invaluable-guide-to-microservices-2d06bd7bcf5d Challenges: • Operational Complexity • Deployment • Multiple databases and transaction management • Communication • The Complexity of a Distributed System
6. From Microservices to Orchestration https://kubernetes.io/docs/concepts/overview/what-is-kubernetes/ • Service discovery and load balancing • Storage orchestration • Automated rollouts and rollbacks • Automatic bin packing • Self-healing • Secret and configuration management
7. From Orchestration to Service Mesh https://www.plugandplaytechcenter.com/resources/what-service-mesh-and-why-should-you-care-about-it/ • Traffic Management • Observability • Policy Enforcement • Service Identity and Security
8. Service Mesh
9. Service Mesh A service mesh is a way to increase the observability, resilience and security in a large-scale containerized application. • Separates applications from app networking. • Decouples operation from development
10. Why Service Mesh Makes Sense • Traffic Management ◦ Request retries, timeouts ◦ Traffic splitting/shifting ◦ Faults injections ◦ Circuit breakers • Observability ◦ Rich metrics ◦ Distributed tracing ◦ Access logs • Security ◦ Mutual TLS ◦ authentication, authorization and audit (AAA)
11. Traffic Director
12. What is Traffic Director • Enterprise-ready traffic management for open service mesh • Focus on hybrid-cloud and multi-clouds • Fully managed control plane for service mesh • Global load balancing across clusters and VMs in multiple regions • xDS V2 support without lock-ins • Service discovery for endpoints • Demand-driven autoscaling • Request routing and traffic policies • Health checking at scale • Observability
13. What is Traffic Director
14. Traffic Director service discovery
15. Network Endpoint Group
16. Traffic Director load balancing resources to be configured
17. Ingress with external HTTP(s) load balancer
18. Use Cases
19. Traffic Director Use Cases
20. Traffic Director Use Cases
21. Traffic Director Use Cases
22. Demo
23. Traffic Director Use Cases • From monolithic to microservices • Hybrid clouds and multi-clouds
24. References • Service Mesh ◦ https://buoyant.io/service-mesh-manifesto/ • Istio ◦ https://istio.io/latest/docs/ops/deployment/deploym ent-models/ • Traffic Director ◦ https://cloud.google.com/load-balancing/docs ◦ https://cloud.google.com/traffic-director/docs/setti ng-up-traffic-director ◦ https://cloud.google.com/traffic-director/docs/set-u p-gke-pods-auto • Envoy ◦ https://www.envoyproxy.io/docs/envoy/latest/intro/a rch_overview/upstream/load_balancing/priority#arch- overview-load-balancing-priority-levels
25. THANK YOU