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

Backport of [NET-9510] Document known OpenShift issue for consul-k8s 1.2.x, 1.3.x and 1.4.x into release/1.18.x (#21229) 

* backport of commit 9c08582a74

* backport of commit 1e57409548

---------

Co-authored-by: Nathan Coleman <nathan.coleman@hashicorp.com>
pull/21248/head
hc-github-team-consul-core 2024-05-28 14:25:33 -07:00 committed by GitHub
parent c5fec4df22
commit 3b3c028351
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
website/content/docs/release-notes/consul-k8s/v1_2_x.mdx
View File

@ -75,6 +75,14 @@ We are pleased to announce the following Consul updates.
For more detailed information, please refer to the [upgrade details page](/consul/docs/upgrading/upgrade-specific) and the changelogs. For more detailed information, please refer to the [upgrade details page](/consul/docs/upgrading/upgrade-specific) and the changelogs.
## Known Issues
The following issues are known to exist in the v1.2.x releases. Refer to the changelog for more information.
- v1.2.8 - Service-to-service networking is broken when deployed on OpenShift. OpenShift users are advised to avoid deploying this version of consul-k8s.
A fix is present in the v1.2.9 release [[GH-4038](https://github.com/hashicorp/consul-k8s/pull/4038)].
## Changelogs ## Changelogs
The changelogs for this major release version and any maintenance versions are listed below. The changelogs for this major release version and any maintenance versions are listed below.

2
website/content/docs/release-notes/consul-k8s/v1_3_x.mdx
View File

@ -45,6 +45,8 @@ For more detailed information, please refer to the [upgrade details page](/consu
The following issues are known to exist in the v1.3.x releases. Refer to the changelog for more information. The following issues are known to exist in the v1.3.x releases. Refer to the changelog for more information.
- When using the v2 API with transparent proxy, Kubernetes pods cannot use L7 liveness, readiness, or startup probes. - When using the v2 API with transparent proxy, Kubernetes pods cannot use L7 liveness, readiness, or startup probes.
- v1.3.5 - Service-to-service networking is broken when deployed on OpenShift. OpenShift users are advised to avoid deploying this version of consul-k8s.
A fix is present in the v1.3.6 release [[GH-4037](https://github.com/hashicorp/consul-k8s/pull/4037)].
## Changelogs ## Changelogs

7
website/content/docs/release-notes/consul-k8s/v1_4_x.mdx
View File

@ -41,6 +41,13 @@ Refer to [Supported Consul and Kubernetes versions](/consul/docs/v1.18.x/k8s/com
For more detailed information, please refer to the [upgrade details page](/consul/docs/upgrading/upgrade-specific) and the changelogs. For more detailed information, please refer to the [upgrade details page](/consul/docs/upgrading/upgrade-specific) and the changelogs.
## Known issues
The following issues are known to exist in the v1.4.x releases:
- v1.4.2 - Service-to-service networking is broken when deployed on OpenShift. OpenShift users are advised to avoid deploying this version of consul-k8s.
A fix is present in the v1.4.3 release [[GH-4034](https://github.com/hashicorp/consul-k8s/pull/4034)].
## Changelogs ## Changelogs
The changelogs for this major release version and any maintenance versions are listed below. The changelogs for this major release version and any maintenance versions are listed below.