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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #21224 to be assessed for backporting due to the inclusion of the label backport/1.18.
The below text is copied from the body of the original PR.
Description
hashicorp/consul-k8s#3813 was recently reverted due to broken service→service networking when deployed on OpenShift. This change is to document the consul-k8s releases that should not be consumed on OpenShift as a result and point to the fix in the subsequent patch releases.
Note
This will need to be backported to 1.18, 1.17 and 1.16 in order to cover the corresponding docs for each version of consul-k8s that was impacted.
Testing & Reproduction steps
N/A
Links
Docs deployed with change
PR Checklist
Overview of commits