Mirror of Istio: Connect, secure, control, and observe services.
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.
Johan Dewe bd7e445fd7 Remove trailing tab chars from each line ending. (#13570) 13 hours ago
.circleci update to go1.12 (#13531) 2 days ago
.github Simplified issue templates. (#13380) 1 week ago
bin make GC more aggressive (#13596) 1 day ago
docker Merge release-1.1 into master (#11096) 3 months ago
galley Enable more linters and fix warnings/errors. (#13245) 1 week ago
install Remove trailing tab chars from each line ending. (#13570) 13 hours ago
istioctl Do not use sh in istioctl. (#13395) 19 hours ago
mixer update to go1.12 (#13531) 2 days ago
pilot cleans up unnecessary left over comment (#13137) 14 hours ago
pkg Add integration tests for Istio authorization for groups and list claims (#13557) 21 hours ago
prow New prow e2e Multi-cluster test for Split Horizon EDS (#12709) 4 days ago
release Fix again helm copy, was reverted during merge from release 1.1 (#13337) 1 week ago
samples update jinja and urllib3 (#13585) 1 day ago
security Fix several lint issues on Citadel Agent. (#13558) 23 hours ago
tests For RBAC v2, add integration tests for authorization of groups and list claims (#13628) 15 hours ago
tools Merge branch 'release-1.1' into master-merge-1.1 6 days ago
vendor add istioctl experimental auth for checking TLS/JWT/RBAC setting on a pod. (#12774) 1 day ago
.codecov.yml Include js/css files into static folder (#12983) 1 week ago
.gitattributes add missing .pb.go to list of generated files (#12419) 1 month ago
.gitignore Remove Servicegraph, and therefore addons. (#12470) 6 days ago
.golangci.yml attempt to update golangcilint (#13525) 3 days ago
CONTRIBUTING.md Add a local CONTRIBUTING.md file that points to the main one on istio/community. (#1871) 1 year ago
Gopkg.lock add istioctl experimental auth for checking TLS/JWT/RBAC setting on a pod. (#12774) 1 day ago
Gopkg.toml add istioctl experimental auth for checking TLS/JWT/RBAC setting on a pod. (#12774) 1 day ago
LICENSE Another license fix. 1 year ago
Makefile move istioctl completion generator to its own target (#13567) 2 days ago
OWNERS Clean up owners a tad. (#8695) 7 months ago
OWNERS_ALIASES Adding aliases for OWNERS (#13194) 2 weeks ago
README.md fix broken links in readme. (#13610) 22 hours ago
codecov.skip Include js/css files into static folder (#12983) 1 week ago
codecov.threshold Fix MCP dial-out mode. (#13399) 1 week ago
istio.deps add upstream_transport_failure_reason to access log (#12434) 2 weeks ago



CircleCI Go Report Card GoDoc codecov.io GolangCI

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

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, Mesos, etc.

Visit istio.io for in-depth information about using Istio.

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.