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.
Ralf Pannemans 0914c96da9 Move missing imagePullSecrets to ServiceAccount (#11661) 7 hours ago
.circleci Revert "Merge release-1.1 to master (#11722)" (#11761) 1 week ago
.github Adding "kind/test failure" to stalebot exempt list (#9870) 3 months ago
addons update linters (#10809) 1 month ago
bin Revert "Merge release-1.1 to master (#11722)" (#11761) 1 week ago
docker Merge release-1.1 into master (#11096) 1 month ago
galley Revert "Merge release-1.1 to master (#11722)" (#11761) 1 week ago
install Move missing imagePullSecrets to ServiceAccount (#11661) 7 hours ago
istioctl Add verify_test.go to unit test "istioctl verify-install" (#11794) 2 days ago
mixer Revert "Merge release-1.1 to master (#11722)" (#11761) 1 week ago
pilot Update istioctl authn tls-check to take into account caller proxy (#11603) 5 days ago
pkg Automatically populate the GCP zone in the proxy bootstrap (#11607) 5 days ago
prow Revert "Merge release-1.1 to master (#11722)" (#11761) 1 week ago
release Revert "Merge release-1.1 to master (#11722)" (#11761) 1 week ago
samples Revert "Merge release-1.1 to master (#11722)" (#11761) 1 week ago
security remove ServiceAccount update event handler (#11775) 6 days ago
tests Fix tests param: istioNamespace (#11780) 6 days ago
tools Revert "Merge release-1.1 to master (#11722)" (#11761) 1 week ago
vendor Revert "Merge release-1.1 to master (#11722)" (#11761) 1 week ago
.codecov.yml hide test package coverage (#10433) 2 months ago
.gitattributes Enable MCP by default in helm values and e2e tests (#10222) 2 months ago
.gitignore Revert "Merge release-1.1 to master (#11722)" (#11761) 1 week ago
.golangci.yml ci: simplify code with unparam linter (#9990) 3 months ago
CONTRIBUTING.md Add a local CONTRIBUTING.md file that points to the main one on istio/community. (#1871) 1 year ago
Gopkg.lock Revert "Merge release-1.1 to master (#11722)" (#11761) 1 week ago
Gopkg.toml Revert "Merge release-1.1 to master (#11722)" (#11761) 1 week ago
LICENSE Another license fix. 1 year ago
Makefile Revert "Merge release-1.1 to master (#11722)" (#11761) 1 week ago
OWNERS Clean up owners a tad. (#8695) 5 months ago
README.md Rename node agent in README.md (#11751) 6 days ago
codecov.skip Revert "Merge release-1.1 to master (#11722)" (#11761) 1 week ago
codecov.threshold Update codecov to use skip file as threshold as well (#11294) 3 weeks ago
envoy.test Support customization of Envoy bootstrap config (#11559) 1 week ago
istio.deps Revert "Merge release-1.1 to master (#11722)" (#11761) 1 week ago

README.md

Istio

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.

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.

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

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