istio/ztunnel

The `ztunnel` component of ambient mesh

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓Open shareable report →

istio/ztunnel has 450+ stars and 150+ forks on GitHub, is written in Rust, and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on October 15th, 2026
Created on October 19th, 2022
Open Issues & Pull Requests: 130 (+0)
GitHub issues: Enabled
Number of forks: 195
Total Stargazers: 489 (+0)
Total Subscribers: 31 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.2 hours
Mean response time: 18.7 days
90th percentile: 24.3 days
Tracked items: 115

How this project is maintained

About 11% of issues opened in the past year have never received a reply. 76% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 57% of issues opened in the past year have been closed. Three people close 60% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 51
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 437 days
Stale 30+ days: 48
Stale 90+ days: 39

Recent activity

Opened in 7 days: 0
Closed in 7 days: 1
Comments in 7 days: 6
Events in 7 days: 12

Top labels

  • area/traffic-flow (3)
  • area/configurability (2)
  • feature/multi-cluster (2)
  • kind/enhancement (2)
  • size/S (2)
  • windows (2)
  • OSS Alpha (1)
  • P0 (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Ztunnel is a node proxy component for Istio's ambient mesh that handles encrypted traffic routing without terminating user HTTP connections.

Ztunnel solves the problem of providing transparent, encrypted communication between workloads in a Kubernetes cluster as part of the ambient mesh architecture. Rather than intercepting and processing application traffic, it operates at the node level to establish secure tunnels between nodes, leaving HTTP processing to dedicated proxies. The implementation prioritizes simplicity and performance by maintaining a deliberately narrow feature set, implementing only what the ambient mesh node proxy requires.

Ztunnel is suited for organizations adopting Istio's ambient mesh mode who need a lightweight, purpose-built node proxy. It explicitly avoids generic extensibility features like external authorization, WASM, or Lua scripting, positioning itself as a complement to Envoy rather than a replacement. Teams should choose this if they want the ambient mesh architecture without the overhead of a full-featured proxy at the node level. The project is not appropriate for use cases requiring HTTP traffic termination or custom policy extensions.

The project maintains active development with regular commits addressing both features and maintenance. Pull requests receive timely review and feedback from maintainers. The codebase shows consistent attention to security considerations, particularly around cryptographic implementations, with support for multiple TLS providers including AWS-LC, Ring, Boring, and OpenSSL, and special handling for FIPS compliance requirements. The project documentation includes detailed architecture specifications and build guidance for different deployment scenarios.