github
/
consul
mirror of https://github.com/hashicorp/consul
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Backport of docs: Update release notes with Envoy compat issue into release/1.15.x (#16496) 

* backport of commit f189a8203c

* backport of commit 82d9805943

* backport of commit f1d95252a8

* backport of commit 1c8d737bee

---------

Co-authored-by: David Yu <dyu@hashicorp.com>
pull/16504/head
hc-github-team-consul-core 2023-03-01 16:22:40 -06:00 committed by GitHub
parent cf743a36b7
commit 0b85dc39a2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
website/content/docs/release-notes/consul/v1_15_x.mdx
View File

@ -68,6 +68,18 @@ For more detailed information, please refer to the [upgrade details page](/consu
The following issues are known to exist in the v1.15.0 release:
- For v1.15.0, Consul is reporting newer releases of Envoy (for example, v1.25.1) as not supported, even though these versions are listed as valid in the [Envoy compatilibity matrix](/consul/docs/connect/proxies/envoy#envoy-and-consul-client-agent). The following error would result for newer versions of Envoy:
```log hideClipboard
Envoy version 1.25.1 is not supported. If there is a reason you need to use this version of envoy use the ignore-envoy-compatibility flag. Using an unsupported version of Envoy is not recommended and your experience may vary.
```
The workaround to resolve this issue until Consul v1.15.1 would be to run the client agents with the new `ingore-envoy-compatiblity` flag:
```shell-session
$ consul connect envoy --ignore-envoy-compatibility
```
- For v1.15.0, there is a known issue where `consul acl token read -self` requires an `-accessor-id`. This is resolved in the uppcoming Consul v1.15.1 patch release.
- For v1.15.0, there is a known issue where search filters produced errors and resulted in lists not showing full results until being interacted with. This is resolved in the upcoming Consul v1.15.1 patch release.