1 views collected around this technical thread.
This article explains how to achieve zero‑trust security in Kubernetes by using a service mesh such as Linkerd, covering workload identity, mTLS, certificate management, policy definition with CRDs, and the practical limitations of mesh‑based protection.
This article explains how to prepare Linkerd for production use by covering high‑availability deployment, Helm chart installation, Prometheus metric handling, external Prometheus integration, multi‑cluster communication, and additional operational best‑practices such as resource tuning and security considerations.
This article explains the concept of microservices, compares them with traditional monolithic web applications, outlines their advantages and challenges, and introduces first‑generation frameworks like Spring Cloud and Dubbo as well as next‑generation service‑mesh solutions such as Linkerd, Envoy, Istio, and Conduit, especially in Kubernetes environments.
After two years of using Istio in production, the author explains the operational complexities, reliability issues, and protocol limitations that led to abandoning Istio in favor of Linkerd, highlighting the pros and cons of both service meshes within Kubernetes environments.
Linkerd 2.8 adds a multi‑cluster extension that securely connects Kubernetes clusters across any network topology, introduces an add‑on plugin system with Jaeger and Grafana support, and includes numerous performance and stability improvements for cloud‑native service mesh deployments.
This article explains the concept, architecture, and evolution of Service Mesh, distinguishes it from related technologies, describes its core functions and a typical Linkerd request flow, and discusses why it has become essential for modern cloud‑native microservice environments.