Skip to content
No description, website, or topics provided.
Branch: maistra-0.11
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci No longer build 0.8, but do 1.1 (#12401) Mar 11, 2019
.github Change istio-auth enabled or not to installation (#8632) Sep 12, 2018
addons update linters (#10809) Jan 8, 2019
bin Get rid of subcharts (#11767) Feb 15, 2019
docker
galley
install Update sidecar injector to create/monitor/update webhook configuratio… Apr 11, 2019
istioctl enhance verify install command (#12174) Mar 21, 2019
mixer
pilot
pkg Drop log level for missing service account for spiffe uri (#12239) Mar 21, 2019
prow Various fixes for the Multicluster e2e test [release-1.1] (#11940) Mar 4, 2019
release
samples add samples for the route directive demo (#12524) Mar 15, 2019
security Fix identity in certs provisioned for VMs. (#12109) Feb 28, 2019
tests Revert #11522: fix routing when DNS is resolved (#12365) Mar 8, 2019
tools
vendor Build 1.1.1 (#12690) Mar 22, 2019
.codecov.yml
.gitattributes Enable MCP by default in helm values and e2e tests (#10222) Dec 3, 2018
.gitignore
.golangci.yml ci: simplify code with unparam linter (#9990) Nov 16, 2018
CONTRIBUTING.md Add a local CONTRIBUTING.md file that points to the main one on istio… Nov 27, 2017
Gopkg.lock
Gopkg.toml
LICENSE Another license fix. May 18, 2017
Makefile Turn policy off by default (#12114) Mar 3, 2019
OWNERS Clean up owners a tad. (#8695) Sep 13, 2018
README.md
codecov.skip Randomize Galley ports for integration testing (#11285) Feb 1, 2019
codecov.threshold Add threshold for rds.go codecov (#12499) Mar 21, 2019
istio.deps Build 1.1.1 (#12690) Mar 22, 2019

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.

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

You can’t perform that action at this time.