Update release notes to indicate folks should upgrade to to 1.16.2 or… (#19019)
Update release notes to indicate folks should upgrade to to 1.16.2 or later (#19002) * Update v1_16_x.mdx * Update upgrade-specific.mdx * Update website/content/docs/upgrading/upgrade-specific.mdx Co-authored-by: Jeff Boruszak <104028618+boruszak@users.noreply.github.com>
This commit is contained in:
parent
f004db21bc
commit
654d29c917
|
@ -81,4 +81,6 @@ The changelogs for this major release version and any maintenance versions are l
|
||||||
|
|
||||||
<Note> These links take you to the changelogs on the GitHub website. </Note>
|
<Note> These links take you to the changelogs on the GitHub website. </Note>
|
||||||
|
|
||||||
- [1.2.0-rc1](https://github.com/hashicorp/consul-k8s/releases/tag/v1.2.0-rc1)
|
- [1.2.0](https://github.com/hashicorp/consul-k8s/releases/tag/v1.2.0)
|
||||||
|
- [1.2.1](https://github.com/hashicorp/consul-k8s/releases/tag/v1.2.1)
|
||||||
|
- [1.2.2](https://github.com/hashicorp/consul-k8s/releases/tag/v1.2.2)
|
||||||
|
|
|
@ -71,8 +71,8 @@ The following issues are known to exist in the v1.16.x releases:
|
||||||
- v1.16.0 - v1.16.1 may have issues when a snapshot restore is performed
|
- v1.16.0 - v1.16.1 may have issues when a snapshot restore is performed
|
||||||
and the servers are hosting xDS streams. When this bug triggers, it
|
and the servers are hosting xDS streams. When this bug triggers, it
|
||||||
will cause Envoy to incorrectly populate upstream endpoints. It is
|
will cause Envoy to incorrectly populate upstream endpoints. It is
|
||||||
currently not recommended for service mesh users running agent-less
|
currently recommended for service mesh users running agent-less
|
||||||
workloads to upgrade Consul to these versions.
|
workloads to upgrade Consul to v1.16.2 and later.
|
||||||
|
|
||||||
## Changelogs
|
## Changelogs
|
||||||
|
|
||||||
|
@ -81,3 +81,5 @@ The changelogs for this major release version and any maintenance versions are l
|
||||||
<Note> These links take you to the changelogs on the GitHub website. </Note>
|
<Note> These links take you to the changelogs on the GitHub website. </Note>
|
||||||
|
|
||||||
- [1.16.0](https://github.com/hashicorp/consul/releases/tag/v1.16.0)
|
- [1.16.0](https://github.com/hashicorp/consul/releases/tag/v1.16.0)
|
||||||
|
- [1.16.1](https://github.com/hashicorp/consul/releases/tag/v1.16.1)
|
||||||
|
- [1.16.2](https://github.com/hashicorp/consul/releases/tag/v1.16.2)
|
||||||
|
|
|
@ -19,8 +19,7 @@ upgrade flow.
|
||||||
#### Known issues
|
#### Known issues
|
||||||
|
|
||||||
Service mesh in Consul versions 1.16.0 and 1.16.1 may have issues when a snapshot restore is performed and the servers are hosting xDS streams.
|
Service mesh in Consul versions 1.16.0 and 1.16.1 may have issues when a snapshot restore is performed and the servers are hosting xDS streams.
|
||||||
When this bug triggers, it will cause Envoy to incorrectly populate upstream endpoints. Due to this issue, it is currently not recommended for
|
When this bug triggers, it causes Envoy to incorrectly populate upstream endpoints. To prevent this issue, service mesh users who run agent-less workloads should upgrade Consul to v1.16.2 or later.
|
||||||
service mesh users running agent-less workloads to upgrade Consul to these versions.
|
|
||||||
|
|
||||||
#### API health endpoints return different status code
|
#### API health endpoints return different status code
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue