ServiceName=userservice • ClusterIP=10.254.162.44 • Domain=userservice.default.svc.cluster.local 2. 生成DNS记录 • userservice.default.svc.cluster.local -> 10.254.162.44 kube-proxy 3. 发送请求 GET http://userservice/id/1000221 1000221 4. 域名解析 • 补全userservice -> userservice.default.svc.cluster.local • 解析域名 userservice.default.svc.cluster.local • 得到Cluster IP (10.254.162.44) 5. kube-proxy拦截到10.254.162.44的请求 • 修改目标地址为Pod IP=192 default.svc.cluster.local 2. 生成DNS记录 • userservice.default.svc.cluster.local -> 10.254.162.44 3. 发送请求 GET http://userservice/id/1000221 4. 域名解析 • 补全userservice -> userservice.default.svc.cluster.local •

东西向服务间通讯的特殊桥梁 服务注册中心 Cluster-2 Service-B Edge Sidecar Service-B Service-B Edge Sidecar Edge Sidecar Local Sidecar Service-A 调用服务Service-b 8.8.8.1 8.8.8.2 8.8.8.3 服务注册中心 同步注册信息 Cluster-1 3.转发请求到edge 通过注册中心可以得知 Service-B在Cluster2，和相 应的edge sidecar地址列表 edge-sidecar : 8.8.8.1@cluster2 edge-sidecar : 8.8.8.2@cluster2 edge-sidecar : 8.8.8.3@cluster2 Service-B : 192.168.1.101@cluster2 Service-B : 192.168 168.1.102@cluster2 Service-B : 192.168.1.103@cluster2 edge-sidecar : 8.8.8.1@cluster2 edge-sidecar : 8.8.8.2@cluster2 edge-sidecar : 8.8.8.3@cluster2 Service-B@zone2 4. Edge sidecar执行服务发现并 转发请求给Servi

2 com.svc.role -> 172.168.1.2 com.svc.zoo -> 172.168.1.3 user.default.svc.cluster.local -> 172.168.1.2 zoo.default.svc.cluster.local -> 172.168.1.3 APP user interface com.svc.user Interface com.svc.role Labels interface user version 1.0.0 User Service clusterIP 172.168.1.2 domain user.default.svc.cluster.local POD APP user interface com.svc.user Interface com.svc.role Labels interface role version interface com.svc.zoo Labels version 1.0.0 Zoo Service clusterIP 172.168.1.3 domain zoo.default.svc.cluster.local POD APP zoo interface com.svc.zoo Labels version 2.0.0落地形态 Traffic RulesSOFA MOSN Virtual

Improved staleness semanticPrometheus at scale ● In the old days… ○ one or more prometheus per cluster ○ hashmod sharding Node Node Node Node Node Node Node Node Node Hashmod = 0 Hashmod = prometheus1 prometheus2Prometheus at scale ● In the old days… ○ one or more prometheus per cluster ○ hashmod sharding Almost works... prometheus prometheus prometheus prometheus Old-schooled federation ● “Slave” prometheis collecting metrics for one cluster. ● Top level prometheus scraping from slaves. ● Top level prometheus as a query entry point.

主流流量 JavaApp Local Proxy OSP Server Service Registry Service Config Center Remote Proxy Cluster API Gateway 备用链路 服务发现 服务注册 配置下发 服务路由 网络传输 OSP client多语言客户端接入 • HTTP & TCP • Local & Remote 根据接入对象的不同，制定 不同的接入策略，达到 • 接入简单 • 保证性能 • 节省资源 Java App Local Proxy OSP Server Remote Proxy Cluster Thrift over TCP PHP App C/C++/Node JS App Thrift over TCP Thrift over TCP JSON over address File Pod Remote Proxy Cluster 主流量 备用或限流 DaemonsetOverall JavaApp Local Proxy OSP Server Service Registry Service Config Center Remote Proxy Cluster API Gateway 备用链路 服务发现 服务注册

Mesh实践 - WeiboMesh ➢ Cluster（发现集群管理理，group + path） ➢ HA（⾼高可⽤用策略略） ➢ LB（负载均衡） ➢ Endpoint（服务节点的抽象） ➢ Protocol（Motan2/传输协议+Simple/序列列化协议）Service Mesh Meetup · BeiJing Cluster 模块 �18 微博Service Mesh实践 Mesh实践 - WeiboMesh WM/ Client request Server WM/ Server ⽬目标机器器 请求机器器 Client Cluster High Available Load Balance Filter Chain Transport Endpoint Filter Chain Serialize Endpoint EndpointService WeiboMesh php/OR/java Client Weibo Mesh register Filter HA+LB Endpoint Cluster degrade Registry Weibo Mesh motan2 snapshot Endpoint motan2 serialize Register DiscoverService

/013/21 LB\Ingress API Gateway Sidecar App POD Sidecar App POD Traffic Control Plane K8S Cluster API Gateway in Service Mesh4/21 API Gateway Service Mesh vs 南北流量（内外） API Gateway vs Service Mesh Code6/21 LB\Ingress API Gateway Sidecar App POD Sidecar App POD Traffic Control Plane Cluster API Gateway Mesh An infrastructure to expose your services as a managed APIs in the form of a decoupled AdminAPI GDS Validation Diff Store GlobalFilters FilterChains Router Service NET/IO PROTOCOL Cluster Router … Filter Pipeline Extension JavaScript Lua GoPlugin ScriptFilter File Istio xds rest

is used for sidecar proxies in the application containers. ii. "ingress" Ingress type is used for cluster ingress proxies. iii. "router" Router type is used for standalone proxies acting as L7/L4 routers role.Domain Kubernetes 环境变量INSTANCE_IP 环境变量POD_NAME.环境变量POD _NAMESPACE 环境变量POD_NAMESPACE.svc. cluster.local Consul private IP,默认127.0. 0.1 IPAddress.service.consul service.consul Other private IP

version 同左 Instance Work load 同左 Endpoint Path - 26/28维度匹配-service 命名规则 Version|App|Namespace|Cluster v1|projuctpage|bookinfo|product-demo 27/28感谢聆听 欢迎关注，获取最新分布式架构内容 关注服务网格，关注 ServiceMesher

资源 云化 资源 基础 服务 蚂蚁 k8s 核心 CRI Kubernetes API Server 极速交付 分时复用 弹性容量 资源画像 规模化调度 高可用容灾 可视化 服务 Cluster Control Panel 在线应用 计算型混部任务 CSI CNI Device Plugin runc nanovisor 日志服务 云盘 本地多盘 弹性网卡 网络安全组 GPU