From 44e2aea78a0bb89579014fda0e312c8c22a2514c Mon Sep 17 00:00:00 2001 From: David Yu Date: Wed, 27 Sep 2023 12:32:40 -0700 Subject: [PATCH] =?UTF-8?q?Update=20release=20notes=20to=20indicate=20folk?= =?UTF-8?q?s=20should=20upgrade=20to=20to=201.16.2=20or=E2=80=A6=20(#19019?= =?UTF-8?q?)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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> --- website/content/docs/release-notes/consul-k8s/v1_2_x.mdx | 4 +++- website/content/docs/release-notes/consul/v1_16_x.mdx | 6 ++++-- website/content/docs/upgrading/upgrade-specific.mdx | 3 +-- 3 files changed, 8 insertions(+), 5 deletions(-) diff --git a/website/content/docs/release-notes/consul-k8s/v1_2_x.mdx b/website/content/docs/release-notes/consul-k8s/v1_2_x.mdx index 4f34764a496b..59d2c2b21c59 100644 --- a/website/content/docs/release-notes/consul-k8s/v1_2_x.mdx +++ b/website/content/docs/release-notes/consul-k8s/v1_2_x.mdx @@ -81,4 +81,6 @@ The changelogs for this major release version and any maintenance versions are l These links take you to the changelogs on the GitHub website. -- [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) diff --git a/website/content/docs/release-notes/consul/v1_16_x.mdx b/website/content/docs/release-notes/consul/v1_16_x.mdx index a3c14525425a..e414c02b61d3 100644 --- a/website/content/docs/release-notes/consul/v1_16_x.mdx +++ b/website/content/docs/release-notes/consul/v1_16_x.mdx @@ -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 and the servers are hosting xDS streams. When this bug triggers, it will cause Envoy to incorrectly populate upstream endpoints. It is - currently not recommended for service mesh users running agent-less - workloads to upgrade Consul to these versions. + currently recommended for service mesh users running agent-less + workloads to upgrade Consul to v1.16.2 and later. ## Changelogs @@ -81,3 +81,5 @@ The changelogs for this major release version and any maintenance versions are l These links take you to the changelogs on the GitHub website. - [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) diff --git a/website/content/docs/upgrading/upgrade-specific.mdx b/website/content/docs/upgrading/upgrade-specific.mdx index 985e93c98a5d..d621ea4a2733 100644 --- a/website/content/docs/upgrading/upgrade-specific.mdx +++ b/website/content/docs/upgrading/upgrade-specific.mdx @@ -19,8 +19,7 @@ upgrade flow. #### 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. -When this bug triggers, it will cause Envoy to incorrectly populate upstream endpoints. Due to this issue, it is currently not recommended for -service mesh users running agent-less workloads to upgrade Consul to these versions. +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. #### API health endpoints return different status code