Apache Kafka with Istio on K8s
JKS or PKCS12 or PEM format Challenges – Kafka broker SSL with client auth 5 • Certificate renewal requires keystore and truststore regeneration • Broker pods need restarting to pick up the modified0 码力 | 14 页 | 875.99 KB | 1 年前3全栈服务网格 - Aeraki 助你在 Istio 服务网格中管理任何七层流量
in a Typical Microservice Application Service Service Service Service Service Service Message Broker RPC RPC RPC Message Message Message Cache RDB NoSQL We need to manage multiple types of0 码力 | 29 页 | 2.11 MB | 1 年前3Optimal Canary Deployments using Istio and how it scores over Spring Cloud and Kubernetes
Service Instance V1 SPRING CLOUD GATEWAY www.my-application.com 75% or Header: X-User-Type: Non-Admin RIBBON (Client-Side Load Balancer) 25% or Header: X-User-Type: Admin Service Instance V1 Service Service Instance V1 Service Instance V2 Service Instance V1 Service Instance V1 Service Instance V1 My-data-service Service Service Instance V2 SPRING EUREKA Cross-version Traffic Service Instance V1 SPRING CLOUD GATEWAY www.my-application.com 75% or Header: X-User-Type: Non-Admin RIBBON (Client-Side Load Balancer) 25% or Header: X-User-Type: Admin Service Instance V1 Service0 码力 | 9 页 | 1011.00 KB | 1 年前3Observability and Istio Telemetry
uses the name you defined in platform such as Istio. • Service Instance. Each one workload in the Service group is named as an instance. Like pods in Kubernetes, it doesn't need to be a single process process in OS. Also if you are using instrument agents, an instance is actually a real process in OS. • Endpoint. It is a path in the certain service for incoming requests, such as HTTP URI path or gRPC new storage entities ENTITY TYPE DESCRIPTION INVENTORAY Inventory includes service, service_instance, endpoint, network_address. They are metadata for SkyWalking. Don’t delete these. INDICATOR0 码力 | 21 页 | 5.29 MB | 5 月前3Istio Security Assessment
created before other users’ legitimate VirtualServices. Note: During testing, NCC Group observed an instance of a later created VirtualService being able to gain precedence over an earlier created one, but In other words, the Gateway resource must reside in the same namespace as the gateway workload instance. Such behavior could be configured by setting the PILOT_SCOPE_GATEWAY_TO_NAMESPACE environment Istio Location • istio/istio/pilot/tools/debug/pilot_cli.go (line 248) • istio/istio/pkg/envoy/instance.go (line 172) • istio/istio/mixer/pkg/perf/run.go (line 106) • istio/istio/tools/istio-iptables0 码力 | 51 页 | 849.66 KB | 1 年前3Istio控制平面组件原理解析
unique identifier for the source workload instance. kubernetes://redis- master-2353460263- 1ecey.my-namespace source.ip ip_address Source workload instance IP address. 10.0.0.117 source.labels map[string map[string, string] A map of key-value pairs attached to the source instance. version => v1 destination.port int64 The recipient port on the server IP address. 8080 request.time timestamp The timestamp0 码力 | 30 页 | 9.28 MB | 5 月前3Kubernetes容器应用基于Istio的灰度发布实践
ServcieDiscovery接口上的服务发 现方法和用户配置的规则构造xDS 4. Envoy从Discovery获取xDS,动态 更新 Kubernetes Service Instance Instance Service Endpoint Endpoint Istio Istio & Kubernetes:Mixer attribute Mixer proxy svc0 码力 | 38 页 | 14.93 MB | 1 年前3Kubernetes容器应用基于Istio的灰度发布实践
ServcieDiscovery接口上的服务发 现方法和用户配置的规则构造xDS 4. Envoy从Discovery获取xDS,动态 更新 Kubernet es Service Instance Instance Service Endpoint Endpoint Istio14 Istio & Kubernetes:Mixer attribute Mixer proxy svc0 码力 | 34 页 | 2.64 MB | 5 月前3探讨和实践基于Istio的微服务治理事件监控
Mixer通过通过rpc调用,将属性与日志发送给Adapter。基于Mixer的二次开发的流程 • 编写grpc服务端程序,接收来自mixer的数据,并实现自身业务逻辑 • 编写handler、instance、rule配置文件 • 编译打包adapter,上传至docker仓库 • 编写k8s的deployment和service配置文件 • 部署应用基于Mixer的二次开发Hanlder URL 、证书、缓存选项等等。基于Mixer的二次开发Instances Instances。属性映射。基于Mixer的二次开发Rules Rules。将数据交付给适配器。 定义了一个特定的 Instance 何时调用一个特定的 Handler插件编译和镜像打包 插件的编译 CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build - a -installsuffix0 码力 | 29 页 | 8.37 MB | 5 月前3Istio at Scale: How eBay is building a massive Multitenant Service Mesh using Istio
traffic to restrict config pushed to sidecars ● Main Takeaways ○ P99.9 time from single Pilot instance to 0 - 3,000 sidecars < 1 second ○ Pilot CPU & memory within acceptable limits: < 10 cores, 250 码力 | 22 页 | 505.96 KB | 1 年前3
共 12 条
- 1
- 2