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.
Lin Sun f27f66bafb
rename ca addr from istio-pilot to istiod (#21628)
7 hours ago
.github Update (#18919) 3 months ago
bin Remove legacy Helm installation (#21185) 1 week ago
common Automator: update common-files@master in istio/istio@master (#21552) 12 hours ago
common-protos Release 1 5 common files update (#20394) 1 month ago
docker Remove legacy kubectl image (#21269) 1 week ago
galley Add analyzer that recommends using PeerAuthentication (#20919) 1 day ago
install add sts service call credential type to sd tracer (#21592) 16 hours ago
istioctl Exclude capture inbound on prometheus port 15090 (#21450) 2 days ago
licenses Updated deps (#21531) 9 hours ago
manifests rename ca addr from istio-pilot to istiod (#21628) 7 hours ago
mixer Fix CEL test with golang 1.14 (#21568) 1 day ago
operator rename ca addr from istio-pilot to istiod (#21628) 7 hours ago
pilot Cleanup listener builder (#21548) 9 hours ago
pkg rename ca addr from istio-pilot to istiod (#21628) 7 hours ago
prow Updated deps (#21531) 9 hours ago
release Change curl to error out gracefully for user experience (#21496) 1 day ago
samples Fix for wait_for_gateway (#20599) 3 weeks ago
security deflake tests (#21596) 14 hours ago
tests Updated deps (#21531) 9 hours ago
tools Rename "citadel" cert to "istiod" (#21613) 10 hours ago
.codecov.yml Include js/css files into static folder (#12983) 10 months ago
.gitattributes Hide operator's golden test data changes in pull requests by default (#20368) 1 month ago
.gitignore Enablement of BUILD_WITH_CONTAINER for Istio repository (#19322) 2 months ago Update common files. (#14914) 8 months ago
CODEOWNERS Add TR as owner of commonfiles (#21360) 6 days ago Add a local file that points to the main one on istio/community. (#1871) 2 years ago
LICENSE Automator: update common-files@master in istio/istio@master (#20379) 4 weeks ago
Makefile Automator: update common-files@master in istio/istio@master (#21320) 1 week ago Rename "citadel" cert to "istiod" (#21613) 10 hours ago Place istio/istio on BUILD_WITH_CONTAINER=1 plan (#19937) 3 weeks ago Remove unused badges (#19199) 3 months ago Update common files. (#16989) 5 months ago
codecov.skip Remove hyperistio (#19772) 2 months ago
codecov.threshold Use random seeds for jitter in node agent and update test coverage threshold (#17630) 4 months ago
go.mod Updated deps (#21531) 9 hours ago
go.sum Updated deps (#21531) 9 hours ago
istio.deps Updated deps (#21531) 9 hours ago

Go Report Card GoDoc


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.