API definitions for the Istio project
api
Go to file
Jason Wang 7e12b4ec2f Add v1beta1 for Networking APIs (#1232)
* Add v1beta1 networking APIs

* rebase and regen
2020-01-15 09:42:00 -08:00
.github/ISSUE_TEMPLATE
annotation
authentication/v1alpha1
common
common-protos
dictionaries
envoy/config/filter
kubernetes
licenses
mcp
mesh/v1alpha1
mixer
networking
operator
policy/v1beta1
python
rbac/v1alpha1
releaselocks
scripts
security/v1beta1
type/v1beta1
.gitattributes
.gitignore
BUGS-AND-FEATURE-REQUESTS.md
BUILD
CODEOWNERS
CONTRIBUTING.md
GUIDELINES.md
LICENSE
Makefile
Makefile.core.mk
Makefile.overrides.mk
README.md
SUPPORT.md
WORKSPACE
cue.yaml
go.mod
go.sum
istio.mesh.v1alpha1.pb.html
proto.lock
prototool.yaml

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.

This repository depends only on the tools repository for tools used during build. This repository will not depend on any other repositories. Except for tools, all other Istio repositories can take a dependency on the api repository.

API Guidelines

When making changes to the protos in this repository, your changes must comply with the API guidelines.

Updating

After the protobuf definitions are updated, the corresponding *pb.go, _pb2.py, *.json and Kubernetes Custom Resource Definition files must be generated by running make clean gen and submitted as part of the same PR as the updated definitions. Also make proto-commit must be run to update the proto.lock file with new changes.

If releasing a new tagged version, please update python/istio-api/setup.py version to reflect.

Backwards Incompatible Changes

If a PR tries to make backwards incompatible changes, it will be blocked by protolock. To force these changes in, install protolock and run protolock commit --force.

You must include a note in your PR that you had to force the protolock and why.