status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Add Consul 1.14.0 known issue. (#15469) 

Co-authored-by: R.B. Boyer <4903+rboyer@users.noreply.github.com>
This commit is contained in:
Derek Menteer 2022-11-18 15:59:57 -06:00 committed by GitHub
parent 6fa8fa4fca
commit 9a8c47d589
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
CHANGELOG.md
View File

@ -1,5 +1,9 @@
## 1.14.0 (November 15, 2022) ## 1.14.0 (November 15, 2022)
KNOWN ISSUES:
* cli: `consul connect envoy` incorrectly enables TLS for gRPC connections when the HTTP API is TLS-enabled.
BREAKING CHANGES: BREAKING CHANGES:
* config: Add new `ports.grpc_tls` configuration option. * config: Add new `ports.grpc_tls` configuration option.

6
website/content/docs/upgrading/upgrade-specific.mdx
View File

@ -29,6 +29,12 @@ earlier. If you operate Consul service mesh using Nomad 1.4.2 or earlier, do not
[hashicorp/nomad#15266](https://github.com/hashicorp/nomad/issues/15266) is [hashicorp/nomad#15266](https://github.com/hashicorp/nomad/issues/15266) is
fixed. fixed.
For 1.14.0, there is a known issue with `consul connect envoy`. If the command is configured
to use TLS for contacting the HTTP API, it will also incorrectly enable TLS for gRPC.
Users should not upgrade to 1.14.0 if they are using plaintext gRPC connections in
conjunction with TLS-encrypted HTTP APIs.
#### Changes to gRPC TLS configuration #### Changes to gRPC TLS configuration
**Make configuration changes** if using [`ports.grpc`](/docs/agent/config/config-files#grpc_port) in conjunction with any of the following settings that enables encryption: **Make configuration changes** if using [`ports.grpc`](/docs/agent/config/config-files#grpc_port) in conjunction with any of the following settings that enables encryption: