Push the istio-cni to gcr.io (#10536)
* Push the istio-cni to gcr.io This fixes the scripting so the istio-cni is pushed daily to gcr.io. * Address review comments Errant debugging left in commit.
|5 hours ago|
|.circleci||2 weeks ago|
|.github||1 month ago|
|addons||1 month ago|
|bin||2 weeks ago|
|docker||2 months ago|
|galley||2 weeks ago|
|install||2 weeks ago|
|istioctl||2 weeks ago|
|mixer||2 weeks ago|
|pilot||1 week ago|
|pkg||2 weeks ago|
|prow||5 days ago|
|release||5 hours ago|
|samples||1 month ago|
|security||2 weeks ago|
|tests||2 weeks ago|
|tools||2 weeks ago|
|vendor||2 weeks ago|
|.codecov.yml||9 months ago|
|.gitattributes||2 weeks ago|
|.gitignore||3 months ago|
|.golangci.yml||1 month ago|
|CONTRIBUTING.md||1 year ago|
|Gopkg.lock||2 weeks ago|
|Gopkg.toml||2 weeks ago|
|LICENSE||1 year ago|
|Makefile||2 weeks ago|
|OWNERS||3 months ago|
|README.md||2 months ago|
|codecov.skip||3 weeks ago|
|codecov.threshold||3 weeks ago|
|downloadIstio.sh||2 months ago|
|istio.deps||2 weeks ago|
|lintconfig_base.json||2 weeks ago|
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:
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.
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:
istio/api. This repository defines component-level APIs and common configuration formats for the Istio platform.
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.