tag-v1.15.0
About the documentation
Introduction
Getting Started
Building and installation
Version history
Configuration reference
Operations and administration
Extending Envoy for custom use cases
API
FAQ
Build
API
How long will the v2 APIs be supported?
How do I configure Envoy to use the v3 API?
If I upgrade to Envoy 1.13+, do I need to use the v3 API?
How does API versioning interact with a new extension?
Which xDS transport and resource versions does my control plane need to support?
How do I support multiple xDS API major versions in my control plane?
What do the v2, v3, vN etc. mean in API package names?
Why are the Envoy xDS APIs versioned? What is the benefit?
What is the status of incremental xDS support?
Debugging
Performance
Configuration
Load balancing
Extensions
envoy
Docs
»
FAQ
»
What do the v2, v3, vN etc. mean in API package names?
View page source
What do the v2, v3, vN etc. mean in API package names?
ΒΆ
See the
API versioning guidelines
.