Skip to content
A solution for large-scale Service Mesh based on Istio.
Go Shell HTML Makefile Python JavaScript Other
Branch: master
Clone or download
#48 Compare This branch is 124 commits ahead, 1581 commits behind istio:master.
Latest commit 58f8bc2 Jun 21, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci Merge branch 'feature/istio-1.1.4' into feature/grade-istio-1.1.4 Jun 5, 2019
.github Change istio-auth enabled or not to installation (istio#8632) Sep 12, 2018
addons update linters (istio#10809) Jan 8, 2019
bin adjust mosn DOWNLOAD_COMMAND Jun 22, 2019
docker Add bionic and deb_slim base images, optimize size for xenial (istio#… Jan 16, 2019
galley Wire-up excluded resource types list to the CRD check and update logg… Feb 28, 2019
install update the tag to 0.5.0-rc.1 Jun 21, 2019
istioctl Merge branch 'feature/istio-1.1.4' into feature/grade-istio-1.1.4 Jun 5, 2019
mixer fix some unit test Jun 14, 2019
pilot fix some unit test Jun 14, 2019
pkg fix some unit test Jun 14, 2019
prow Various fixes for the Multicluster e2e test [release-1.1] (istio#11940) Mar 4, 2019
release Right place to copy data from (istio#13149) Apr 11, 2019
samples Merge branch 'feature/istio-1.1.4' into feature/grade-istio-1.1.4 Jun 5, 2019
security fix some unit test Jun 14, 2019
tools fix some unit test Jun 14, 2019
vendor Merge branch 'feature/istio-1.1.4' into feature/grade-istio-1.1.4 Jun 5, 2019
.codecov.yml hide test package coverage (istio#10433) Dec 13, 2018
.gitattributes Enable MCP by default in helm values and e2e tests (istio#10222) Dec 3, 2018
.gitignore Merge branch 'feature/istio-1.1.4' into feature/grade-istio-1.1.4 Jun 5, 2019
.golangci.yml ci: simplify code with unparam linter (istio#9990) Nov 16, 2018 提交istio代码 Apr 17, 2018
Gopkg.lock Updating shas for istio (istio#13555) Apr 23, 2019
Gopkg.toml Merge branch 'feature/istio-1.1.4' into feature/grade-istio-1.1.4 Jun 5, 2019
LICENSE 提交istio代码 Apr 17, 2018
Makefile adjust download mosn url Jun 21, 2019
OWNERS Clean up owners a tad. (istio#8695) Sep 13, 2018 Merge branch 'feature/istio-1.1.4' into feature/grade-istio-1.1.4 Jun 5, 2019
codecov.skip Randomize Galley ports for integration testing (istio#11285) Feb 1, 2019
codecov.threshold Add threshold for rds.go codecov (istio#12499) Mar 21, 2019
istio.deps update the tag to 0.5.0-rc.1 Jun 21, 2019


CircleCI Go Report Card

SOFAMesh 是基于 Istio 改进和扩展而来的 Service Mesh 大规模落地实践方案。在继承 Istio 强大功能和丰富特性的基础上,为满足大规模部署下的性能要求以及应对落地实践中的实际情况,有如下改进:

  • 采用 Golang 编写的 MOSN 取代 Envoy
  • 合并 Mixer 到数据平面以解决性能瓶颈
  • 增强 Pilot 以实现更灵活的服务发现机制
  • 增加对 SOFA RPC、Dubbo 的支持


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 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.

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

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), node 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.

You can’t perform that action at this time.