You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
FengyunPan2 9e0887f5ce Make tracing.service.type and tracing.service.externalPort work (#17205) 6 hours ago
.github Update to latest version of (#15103) 3 months ago
bin Nuke some superfluous files. (#17303) 18 hours ago
common Nuke some superfluous files. (#17303) 18 hours ago
common-protos Nuke some superfluous files. (#17303) 18 hours ago
docker Upgrade base image to add user istio-proxy (#17255) 2 days ago
galley Enforce correct metadata for analyzers via unit tests (#17243) 2 days ago
install Make tracing.service.type and tracing.service.externalPort work (#17205) 6 hours ago
istioctl Support version for ilbgateway (#17177) 13 hours ago
mixer Nuke some superfluous files. (#17303) 18 hours ago
pilot Recover panics from patching envoyfilters (#17292) 14 hours ago
pkg Fix error message: "the e" => "the proxy" (#17302) 22 hours ago
prow Add perf benchmark test script (#17007) 5 days ago
release Get rid of demo-auth (#17043) 4 days ago
samples Add PodSecurityPolicy yaml files for SDS (#17116) 5 days ago
scripts Add more linters to the lint_modern target. (#17240) 2 days ago
security xds: use golang protobuf (#17132) 2 days ago
sidecar-injector Pin the base image for the 1.3 branch (#16697) 3 weeks ago
tests Build multiple binaries in single command (#17153) 2 days ago
tools fix -h bug (#17253) 2 days ago
.codecov.yml Include js/css files into static folder (#12983) 5 months ago
.gitattributes Update common files. (#16989) 1 week ago
.gitignore Get rid of demo-auth (#17043) 4 days ago Update common files. (#14914) 3 months ago
CODEOWNERS Fix CODEOWNERS typo (#17016) 1 week ago Add a local file that points to the main one on istio/community. (#1871) 1 year ago
LICENSE Import common files into this repo. (#14473) 3 months ago
Makefile Nuke some superfluous files. (#17303) 18 hours ago Nuke some superfluous files. (#17303) 18 hours ago Update common files. (#16989) 1 week ago Add a lint_modern target to start switchinng over to the build container (#17091) 1 week ago Update common files. (#16989) 1 week ago
codecov.skip Fix testing flags showing up in release binaries (#15797) 1 month ago
codecov.threshold change the app handling path register. (#14432) 3 months ago
go.mod xds: use golang protobuf (#17132) 2 days ago
go.sum xds: use golang protobuf (#17132) 2 days ago
istio.deps update proxy sha (#16861) 2 weeks ago

Go Report Card GoDoc GolangCI


An open platform to connect, manage, and secure microservices.

  • For in-depth information about how to use Istio, visit
  • To ask questions and get assistance from our community, visit
  • To learn how to participate in our overall community, visit our community page

In this README:

In addition, here are some other documents you may wish to read:

You’ll find many other useful documents on our Wiki.


Istio is an open platform for providing a uniform way to integrate microservices, manage traffic flow across microservices, enforce policies and aggregate telemetry data. Istio’s control plane provides an abstraction layer over the underlying cluster management platform, such as Kubernetes.

Istio is composed of these components:

  • Envoy - Sidecar proxies per microservice to handle ingress/egress traffic between services in the cluster and from a service to external services. The proxies form a secure microservice mesh providing a rich set of functions like discovery, rich layer-7 routing, circuit breakers, policy enforcement and telemetry recording/reporting functions.

Note: The service mesh is not an overlay network. It simplifies and enhances how microservices in an application talk to each other over the network provided by the underlying platform.

  • Mixer - Central component that is leveraged by the proxies and microservices to enforce policies such as authorization, rate limits, quotas, authentication, request tracing and telemetry collection.

  • Pilot - A component responsible for configuring the proxies at runtime.

  • Citadel - A centralized component responsible for certificate issuance and rotation.

  • Citadel Agent - A per-node component responsible for certificate issuance and rotation.

  • Galley- Central component for validating, ingesting, aggregating, transforming and distributing config within Istio.

Istio currently supports Kubernetes and Consul-based environments. We plan support for additional platforms such as Cloud Foundry, and Mesos in the near future.


The Istio project is divided across a few GitHub repositories.

  • istio/istio. This is the main repository that you are currently looking at. It hosts Istio’s core components and also the sample programs and the various documents that govern the Istio open source project. It includes:

    • security. This directory contains security related code, including Citadel (acting as Certificate Authority), citadel agent, etc.

    • pilot. This directory contains platform-specific code to populate the abstract service model, dynamically reconfigure the proxies when the application topology changes, as well as translate routing rules into proxy specific configuration.

    • istioctl. This directory contains code for the istioctl command line utility.

    • mixer. This directory contains code to enforce various policies for traffic passing through the proxies, and collect telemetry data from proxies and services. There are plugins for interfacing with various cloud platforms, policy management services, and monitoring services.

  • istio/api. This repository defines component-level APIs and common configuration formats for the Istio platform.

  • istio/proxy. The Istio proxy contains extensions to the Envoy proxy (in the form of Envoy filters), that allow the proxy to delegate policy enforcement decisions to Mixer.

Issue management

We use GitHub combined with ZenHub to track all of our bugs and feature requests. Each issue we track has a variety of metadata:

  • Epic. An epic represents a feature area for Istio as a whole. Epics are fairly broad in scope and are basically product-level things. Each issue is ultimately part of an epic.

  • Milestone. Each issue is assigned a milestone. This is 0.1, 0.2, …, or ‘Nebulous Future’. The milestone indicates when we think the issue should get addressed.

  • Priority/Pipeline. Each issue has a priority which is represented by the Pipeline field within GitHub. Priority can be one of P0, P1, P2, or >P2. The priority indicates how important it is to address the issue within the milestone. P0 says that the milestone cannot be considered achieved if the issue isn’t resolved.

We don’t annotate issues with Releases; Milestones are used instead. We don’t use GitHub projects at all, that support is disabled for our organization.