b176b1f660
|
||
|---|---|---|
| .github/ISSUE_TEMPLATE | ||
| analysis/v1alpha1 | ||
| annotation | ||
| authentication/v1alpha1 | ||
| common | ||
| common-protos | ||
| dictionaries | ||
| envoy | ||
| extensions/v1alpha1 | ||
| kubernetes | ||
| label | ||
| licenses | ||
| mcp | ||
| mesh/v1alpha1 | ||
| meta/v1alpha1 | ||
| networking | ||
| operator/v1alpha1 | ||
| releaselocks | ||
| releasenotes | ||
| scripts | ||
| security | ||
| stability | ||
| telemetry/v1alpha1 | ||
| type/v1beta1 | ||
| .gitattributes | ||
| .gitignore | ||
| BUGS-AND-FEATURE-REQUESTS.md | ||
| CODEOWNERS | ||
| CONTRIBUTING.md | ||
| GUIDELINES.md | ||
| LICENSE | ||
| Makefile | ||
| Makefile.core.mk | ||
| Makefile.overrides.mk | ||
| README.md | ||
| SUPPORT.md | ||
| buf.gen-golang.yaml | ||
| buf.gen-noncrd.yaml | ||
| buf.gen.yaml | ||
| buf.yaml | ||
| clean.sh | ||
| cue.yaml | ||
| gen.sh | ||
| github.com | ||
| go.mod | ||
| go.sum | ||
| header.go.txt | ||
| istio.io | ||
| k8s.io | ||
| 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 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.
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.