awesome-repositories.com
Blog
MCP
awesome-repositories.com

Discover the best open-source repositories with AI-powered search.

ExploreCurated searchesOpen-source alternativesSelf-hosted softwareBlogSitemap
ProjectMCP serverAboutHow we rankPress
LegalPrivacyTerms
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
istio avatar

istio/istio

0
View on GitHub↗
38,226 stars·8,325 forks·Go·Apache-2.0·44 viewsistio.io↗

Istio

Istio is a service mesh infrastructure that provides a centralized control plane to manage, secure, and observe communication between distributed microservices. It functions as a policy-driven network traffic controller, enabling developers to route, balance, and secure service-to-service traffic without requiring modifications to application code. The system enforces zero-trust security by utilizing mutual transport layer authentication to verify cryptographic identities for every network request.

The project distinguishes itself through a sidecar-less proxy architecture, which offloads networking tasks to shared infrastructure proxies rather than requiring individual proxies for every container. This approach is complemented by waypoint proxies, which perform deep packet inspection and enforce granular access policies at the application layer. Furthermore, the platform provides a unified connectivity fabric that synchronizes service registry data across multiple clusters, allowing for consistent traffic management and security policy enforcement across disparate network boundaries.

The system operates on a declarative model where a centralized management component continuously reconciles the desired state with the underlying network infrastructure. It supports both transport-layer and application-layer authorization, allowing for precise control over service access based on service accounts and specific request methods. The architecture is designed to simplify operational management and reduce resource overhead while maintaining consistent network behavior across complex, multi-cluster environments.

Features

  • Service Mesh Control Planes - Provides a centralized control plane to push declarative traffic and security policies to distributed proxies.
  • Service Meshes - Provides a control plane for managing communication, security, and observability across distributed microservices.
  • Sidecarless Service Meshes - Intercepts traffic using shared infrastructure proxies to reduce resource overhead.
  • Zero Trust Networking - Enforces strict identity-based access controls and encryption for all service-to-service communication.
  • Ambient Mesh Deployments - Deploys a service mesh architecture that removes sidecar proxies to simplify operations.
  • Microservice Traffic Management - Directs and balances network traffic between distributed services to ensure reliable communication.
  • Network Traffic Controllers - Routes, secures, and monitors application traffic flows between services without requiring code changes.
  • Sidecarless Network Architectures - Optimizes infrastructure performance by offloading networking tasks to shared proxies.
  • Mutual TLS Implementations - Authenticates services using cryptographic identities verified at the transport layer.
  • Zero Trust Frameworks - Enforces mutual authentication and granular access control policies for every network request between microservices.
  • Multicluster Service Meshes - Unifies multiple clusters into a single service mesh environment for cross-cluster traffic management.
  • Waypoint Proxies - Directs application-level traffic through specialized proxies for granular access control and inspection.
  • Cross-Cluster Service Discovery - Synchronizes service registry data across multiple network boundaries to enable seamless cross-cluster communication.
  • Multi-Cluster Connectivity Fabrics - Links disparate service environments into a unified, addressable network for cross-cluster communication.
  • Multi-Cluster Service Connectivity - Links services across different clusters into a unified network for seamless communication.
  • Layer 4 Authorization Policies - Restricts network access by validating service accounts at the transport layer.
  • Layer 7 Authorization Policies - Restricts application-level traffic by enforcing policies based on HTTP methods and service operations.
  • Deployment and Infrastructure - Service mesh for connecting and securing services.
  • Microservices - Microservice management platform.
  • Service Governance and Platforms - Service mesh for traffic management, security, and observability.
  • Service Mesh - Platform for connecting, securing, and observing services.
  • Declarative Infrastructure Reconciliation - Continuously monitors desired state and updates network infrastructure to match requirements.
  • Infrastructure Proxy Orchestrators - Deploys and configures network proxies to handle traffic at the infrastructure level.
  • Mesh Traffic Policy Management - Manages service mesh traffic and security policies via a centralized control plane.
  • Multi-Network Connectivity Tools - Configures individual cluster networks and gateways to enable cross-cluster communication.
  • Service Mesh Migration Tools - Migrates namespaces to ambient mode by reconfiguring traffic flows and removing sidecar injection.

Star history

Star history chart for istio/istioStar history chart for istio/istio

How this analysis was created: This summary and feature list are AI-generated from collected project material and can contain mistakes. Stars, license and language are imported from GitHub. Inclusion does not mean that we have tested or audited this project. Check the source documentation for any feature you depend on. Learn more on our About page.

AI search

Explore more awesome repositories

Describe what you need in plain English — the AI ranks thousands of curated open-source projects by relevance.

Start searching with AI

Projects sharing features with Istio

These projects share indexed features with Istio. Shared tags can include platform or build tooling; verify the primary use case before treating a result as a replacement.
  • linkerd/linkerd2linkerd avatar

    linkerd/linkerd2

    11,424View on GitHub↗

    This project is a service mesh platform designed to manage, secure, and observe service-to-service communication within Kubernetes clusters. It functions as a control plane that orchestrates transparent sidecar proxies, which intercept and manage network traffic to provide reliable connectivity for microservices. By automating the injection of these proxies, the platform ensures that infrastructure-level policies are applied consistently across all workloads without requiring manual configuration changes. The platform distinguishes itself through its focus on zero-trust security and cross-clu

    Gocloud-nativegolangkubernetes
    View on GitHub↗11,424
  • linkerd/linkerdlinkerd avatar

    linkerd/linkerd

    5,316View on GitHub↗

    Linkerd is a Kubernetes service mesh that manages network traffic between microservices. It functions as a transparent networking proxy, layer 7 traffic manager, and mutual TLS security layer, providing observability and reliability for service-to-service communication without requiring changes to application code. The project distinguishes itself through a sidecar-proxy architecture that intercepts TCP and application-level traffic to provide automatic mutual TLS encryption and identity verification. It enables cross-cluster service networking to link multiple clusters and implements cloud-n

    Scalacloud-nativelinkerdservice-discovery
    View on GitHub↗5,316
  • kumahq/kumakumahq avatar

    kumahq/kuma

    3,971View on GitHub↗

    Kuma is a multi-zone service mesh that orchestrates layer 4 and layer 7 network traffic between containers and virtual machines. It utilizes a centralized control plane to manage an Envoy-based data plane, providing a unified network overlay across multiple clouds, clusters, and on-premises environments. The project implements zero-trust network security through identity-based access control and mutual TLS encryption, automatically provisioning certificates to verify service identities. It supports multi-mesh management, allowing a single control plane to coordinate several independent or iso

    Goapiscloud-nativecncf
    View on GitHub↗3,971
  • emissary-ingress/emissaryemissary-ingress avatar

    emissary-ingress/emissary

    4,509View on GitHub↗

    Emissary is a Kubernetes API gateway that manages incoming external traffic and routes it to internal microservices. It utilizes an Envoy proxy as the underlying data plane to handle high-performance traffic routing and protocol translation, with a control plane that translates Kubernetes custom resources and annotations into proxy configurations. The project provides specialized support for gRPC infrastructure, including HTTP/2 routing and gRPC-Web protocol bridging for browser-based clients. It enables zero-trust security through mutual TLS encryption and delegates identity verification to

    Pythonambassadorapi-gatewayapi-management
    View on GitHub↗4,509
Compare all 30 related projects→

Frequently asked questions

What does istio/istio do?

Istio is a service mesh infrastructure that provides a centralized control plane to manage, secure, and observe communication between distributed microservices. It functions as a policy-driven network traffic controller, enabling developers to route, balance, and secure service-to-service traffic without requiring modifications to application code. The system enforces zero-trust security by utilizing mutual transport layer authentication to verify cryptographic identities…

What are the main features of istio/istio?

The main features of istio/istio are: Service Mesh Control Planes, Service Meshes, Sidecarless Service Meshes, Zero Trust Networking, Ambient Mesh Deployments, Microservice Traffic Management, Network Traffic Controllers, Sidecarless Network Architectures.

Which projects share features with istio/istio?

Projects with overlapping indexed features include: linkerd/linkerd2 — This project is a service mesh platform designed to manage, secure, and observe service-to-service communication… linkerd/linkerd — Linkerd is a Kubernetes service mesh that manages network traffic between microservices. It functions as a transparent… kumahq/kuma — Kuma is a multi-zone service mesh that orchestrates layer 4 and layer 7 network traffic between containers and virtual… emissary-ingress/emissary — Emissary is a Kubernetes API gateway that manages incoming external traffic and routes it to internal microservices.… submariner-io/submariner — Submariner is a tool for connecting pods and services across separate Kubernetes clusters into a unified network mesh.… cilium/cilium — Cilium is a networking, security, and observability platform for containerized environments that leverages…