distributed-tracing-system icon indicating copy to clipboard operation
distributed-tracing-system copied to clipboard

Published 20 hours ago • verified publisher icon maguowei

ref

Open maguowei opened this issue 5 years ago • 5 comments

maguowei avatar May 11 '19 06:05 maguowei

skywalking

maguowei avatar May 17 '19 10:05 maguowei

https://kubernetes.io/zh/docs/concepts/workloads/controllers/daemonset/ Communicating with Daemon Pods Some possible patterns for communicating with Pods in a DaemonSet are:

Push: Pods in the DaemonSet are configured to send updates to another service, such as a stats database. They do not have clients. NodeIP and Known Port: Pods in the DaemonSet can use a hostPort, so that the pods are reachable via the node IPs. Clients know the list of node IPs somehow, and know the port by convention. DNS: Create a headless service with the same pod selector, and then discover DaemonSets using the endpoints resource or retrieve multiple A records from DNS. Service: Create a service with the same Pod selector, and use the service to reach a daemon on a random node. (No way to reach specific node.)

maguowei avatar May 23 '19 03:05 maguowei

https://chinagdg.org/2019/05/opentelemetry-the-merger-of-opencensus-and-opentracing/ https://www.cncf.io/blog/2019/05/21/a-brief-history-of-opentelemetry-so-far/

maguowei avatar May 23 '19 10:05 maguowei

maguowei avatar May 30 '19 05:05 maguowei

maguowei avatar Sep 27 '20 10:09 maguowei