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.
john-a-joyce ab79844e47 Push the istio-cni to gcr.io (#10536) 5 hours ago
.circleci Merge pull request #10256 from ayj/cherry-pick-10222 2 weeks ago
.github Adding "kind/test failure" to stalebot exempt list (#9870) 1 month ago
addons ci: use golangci-lint (#9970) 1 month ago
bin Update go version to 1.11 in circle tests. (#10212) 2 weeks ago
docker Build Istio's own kubectl container (#8934) 2 months ago
galley Fix merge errros, gometalinter off, circle go1.11 2 weeks ago
install Merge pull request #10256 from ayj/cherry-pick-10222 2 weeks ago
istioctl Fix merge errros, gometalinter off, circle go1.11 2 weeks ago
mixer Fix merge errros, gometalinter off, circle go1.11 2 weeks ago
pilot Revert "Permit port to domain validation. (#9656)" (#10278) 1 week ago
pkg Update bootstrap config to use stats_matcher to filter metrics gen (#10184) 2 weeks ago
prow Delete uneeded release files (#10445) 5 days ago
release Push the istio-cni to gcr.io (#10536) 5 hours ago
samples Use scratch base for tcp-echo sample (#9824) 1 month ago
security Merge pull request #10186 from hklai/1.1-master 2 weeks ago
tests Merge pull request #10256 from ayj/cherry-pick-10222 2 weeks ago
tools Update bootstrap config to use stats_matcher to filter metrics gen (#10184) 2 weeks ago
vendor Updated api 2 weeks ago
.codecov.yml Adding requirement for codecov package (#3884) 9 months ago
.gitattributes Enable MCP by default in helm values and e2e tests (#10222) 2 weeks ago
.gitignore Enable e2e MCP integration with optional presubmit tests (#8192) 3 months ago
.golangci.yml ci: simplify code with unparam linter (#9990) 1 month ago
CONTRIBUTING.md Add a local CONTRIBUTING.md file that points to the main one on istio/community. (#1871) 1 year ago
Gopkg.lock Updated api 2 weeks ago
Gopkg.toml Fix merge errros, gometalinter off, circle go1.11 2 weeks ago
LICENSE Another license fix. 1 year ago
Makefile Merge remote-tracking branch 'upstream/release-1.1' into 1.1-master 2 weeks ago
OWNERS Clean up owners a tad. (#8695) 3 months ago
README.md Remove outdated istio/mixerclient ref in docs (#9305) 2 months ago
codecov.skip Adding metric support to codecov job (#10137) 3 weeks ago
codecov.threshold Update codecov threshold due to non-deterministism (#10132) 3 weeks ago
downloadIstio.sh fix boilerplate error in /bin and /prow (#9024) 2 months ago
istio.deps Fix broken CNI SHA value 2 weeks ago
lintconfig_base.json Fix merge errros, gometalinter off, circle go1.11 2 weeks ago

README.md

Istio

CircleCI Go Report Card GoDoc codecov.io

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.

Introduction

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.

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

Repositories

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.