Backport of docs: Add backwards compatibility for Consul 1.14.x and consul-dataplane in the Envoy compat matrix into release/1.15.x (#16463)

* backport of commit 640855e755

* backport of commit 4df972e792

---------

Co-authored-by: David Yu <dyu@hashicorp.com>
pull/16468/head
hc-github-team-consul-core 2023-02-28 10:39:07 -08:00 committed by GitHub
parent 0fe36dd247
commit a6e7830c9f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions

View File

@ -45,12 +45,12 @@ Consul supports **four major Envoy releases** at the beginning of each major Con
### Envoy and Consul Dataplane
Consul Dataplane is a feature introduced in Consul v1.14. Because each version of Consul Dataplane supports one specific version of Envoy, you must use the following versions of Consul, Consul Dataplane, and Envoy together.
The Consul dataplane component was introduced in Consul v1.14 as a way to manage Envoy proxies without the use of Consul clients. Each new minor version of Consul is released with a new minor version of Consul dataplane, which packages both Envoy and the `consul-dataplane` binary in a single container image. For backwards compatability reasons, each new minor version of Consul will also support the previous minor version of Consul dataplane to allow for seamless upgrades. In addition, each minor version of Consul will support the next minor version of Consul dataplane to allow for extended dataplane support via newer versions of Envoy.
| Consul Version | Consul Dataplane Version (Bundled Envoy Version) |
| ------------------- | ------------------------------------------------- |
| 1.15.x | 1.1.x (Envoy 1.25.x), 1.0.x (Envoy 1.24.x) |
| 1.14.x | 1.0.x (Envoy 1.24.x) |
| 1.14.x | 1.1.x (Envoy 1.25.x), 1.0.x (Envoy 1.24.x) |
## Getting Started