API definitions for the Istio project
api
Go to file
Prashanth Josyula 32bc595e98
Add TraceContextOption enum to ZipkinTracingProvider (#3566)
* Add TraceContextOption enum to ZipkinTracingProvider

Add support for configuring trace context propagation format in Zipkin
tracing provider. This enables users to choose between B3-only headers
(default) or dual B3/W3C header support for better interoperability
with W3C trace context systems.

Changes:
- Add TraceContextOption enum with USE_B3 and USE_B3_WITH_W3C_PROPAGATION values
- Add trace_context_option field to ZipkinTracingProvider message
- Maintain backward compatibility with USE_B3 as default

* Add TraceContextOption enum to ZipkinTracingProvider
Add support for configuring trace context propagation format in Zipkin
tracing provider. This enables users to choose between B3-only headers
(default) or dual B3/W3C header support for better interoperability
with W3C trace context systems.

Changes:
- Add TraceContextOption enum with USE_B3 and USE_B3_WITH_W3C_PROPAGATION values
- Add trace_context_option field to ZipkinTracingProvider message
- Maintain backward compatibility with USE_B3 as default

* Add support for configuring trace context propagation format in Zipkin
tracing provider. This enables users to choose between B3-only headers
(default) or dual B3/W3C header support for better interoperability
with W3C trace context systems.

Changes:
- Add TraceContextOption enum with USE_B3 and USE_B3_WITH_W3C_PROPAGATION values
- Add trace_context_option field to ZipkinTracingProvider message
- Maintain backward compatibility with USE_B3 as default
2025-09-19 04:09:28 -07:00
.devcontainer Automator: update common-files@master in istio/api@master (#3563) 2025-09-08 11:59:45 -07:00
.github
analysis/v1alpha1 run make gen (#3559) 2025-08-28 16:54:06 -04:00
annotation stats: add bootstrap annotations for stats flush and eviction (#3562) 2025-09-18 11:37:27 -07:00
common Automator: update common-files@master in istio/api@master (#3563) 2025-09-08 11:59:45 -07:00
common-protos
dictionaries
envoy run make gen (#3559) 2025-08-28 16:54:06 -04:00
extensions/v1alpha1 run make gen (#3559) 2025-08-28 16:54:06 -04:00
kubernetes
label improve documentation for tag and rev label (#3418) 2025-09-08 13:08:44 -07:00
licenses
mcp run make gen (#3559) 2025-08-28 16:54:06 -04:00
mesh/v1alpha1 Add TraceContextOption enum to ZipkinTracingProvider (#3566) 2025-09-19 04:09:28 -07:00
meta/v1alpha1 run make gen (#3559) 2025-08-28 16:54:06 -04:00
networking run make gen (#3559) 2025-08-28 16:54:06 -04:00
releasenotes Add TraceContextOption enum to ZipkinTracingProvider (#3566) 2025-09-19 04:09:28 -07:00
scripts
security run make gen (#3559) 2025-08-28 16:54:06 -04:00
stability
telemetry run make gen (#3559) 2025-08-28 16:54:06 -04:00
tests
type/v1beta1 run make gen (#3559) 2025-08-28 16:54:06 -04:00
.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
gen.sh
go.mod
go.sum
google
header.go.txt
istio.io

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 gen will 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 buf breaking. If there are legitimate reasons to make these breaking changes forever, the configuration in buf.yaml can be changed. If it is a one-off case, the PR can be force approved skipping the test.