Huabing Blog

路在脚下,心向远方

洞若观火:使用OpenTracing增强Istio的调用链跟踪

第二篇:如何利用Opentracing实现Kafka消息的调用跟踪

本文将接着上一篇继续介绍如何利用OpenTracing来对Kafka异步消息进行跟踪,并将异步消息的跟踪信息加入Istio/Envoy生成的分布式调用跟踪链中进行统一呈现。

开源,社区与朋友们

2019 KubeCon + ClondNativeCon + Open Source Summit有感

奇妙的 2019 KubeCon + ClondNativeCon + Open Source Summit 大会!在这里,我近距离接触了大神 Linus;见到了来自 ServiceMesher 社区的很多朋友;还遇到了搞 Kubernetes 的恩格斯后人!

洞若观火:使用OpenTracing增强Istio的调用链跟踪

第一篇:如何利用Opentracing实现方法级的细粒度跟踪

本文将介绍如何利用OpenTracing来增强Istio/Envoy缺省的调用链跟踪实现:如何利用Opentracing来实现跨进程边界的分布式调用上下文传递;以及在Istio/Envoy生成的分布式调用跟踪基础上实现方法级的细粒度调用跟踪。

Which One is the Right Choice for the Ingress Gateway of Your Service Mesh?

Kubernetes Ingress, Istio Gateway or API Gateway?

By default, in a Kubernetes cluster with the Istio service mesh enabled, services can only be accessed inside the cluster. However, some of the services may need to be exposed to the external network as well. Kubernetes and Istio provide a variety of means to get external traffic into your cluster including NodePort, LoadBalancer, Kubernetes Ingress and Istio Gateway. With all these options, which one should be the right choice for your service mesh running in production?

如何为服务网格选择入口网关?

Kubernetes Ingress, Istio Gateway还是API Gateway?

在启用了Istio服务网格的Kubernetes集群中,缺省情况下只能在集群内部访问网格中的服务,要如何才能从外部网络访问这些服务呢? Kubernetes和Istio提供了NodePort,LoadBalancer,Kubernetes Ingress,Istio Gateway等多种外部流量入口的方式,面对这么多种方式,我们在产品部署中应该如何选择?