* add incremental mcp based on incremental xds Extend the MCP to include support for incremental configuration pushes. This is *heavily* derived from the new incremental xDS protocol. xref: https://github.com/envoyproxy/data-plane-api/blob/master/XDS_PROTOCOL.md#incremental-xds * document initial_resource_versions should only be included in first request * move resource version into metadata |
||
|---|---|---|
| .circleci | ||
| authentication/v1alpha1 | ||
| docker | ||
| envoy/config/filter/http | ||
| mcp | ||
| mesh/v1alpha1 | ||
| mixer | ||
| networking/v1alpha3 | ||
| policy/v1beta1 | ||
| prow | ||
| python | ||
| rbac/v1alpha1 | ||
| scripts | ||
| .gitignore | ||
| BUILD | ||
| LICENSE | ||
| Makefile | ||
| OWNERS | ||
| README.md | ||
| STYLE-GUIDE.md | ||
| WORKSPACE | ||
README.md
Istio APIs and Common Configuration Definitions
This repository defines component-level APIs and common configuration formats for the Istio platform. These definitions are specified using the protobuf syntax.
All other Istio repositories can take a dependency on the api repository. This repository will not depend on any other repos
Standard vocabulary
All components of an Istio installation operate on a shared vocabulary of attributes, as defined in this repo.
Style guide
When designing proto-based APIs in the Istio project, please follow the Istio API Style Guide.
Updating
After the protobuf definitions are updated, the corresponding *pb.go and _pb2.py files must be generated by running scripts/generate-protos.sh and submitted as part of the same PR as the updated definitions.
If releasing a new tagged version, please update python/istio-api/setup.py version to reflect.