OSDOCS-17711: Updates for gAPI 1.5 and OSSM 3.x - #119010
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@jab-rh: This pull request references OSDOCS-17711 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target either version "5.1.0." or "openshift-5.1.0.", but it targets "openshift-5.0" instead. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
Bot
added
the
size/XL
|
|
||
| [NOTE] | ||
| ==== | ||
| Passthrough is exclusive to {product-title} routes when you compare them with `HTTPRoute` CRs. `HTTPRoute` CRs do not support passthrough. For Gateway API passthrough, use a `TLSRoute` CR. For more information, see xref:routing-tls-requests-to-services.adoc#routing-tls-requests-to-services[Route TLS requests to services]. |
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.NoXrefInModules: Do not include xrefs in modules, only assemblies (exception: release notes modules).
| [NOTE] | ||
| ==== | ||
| {product-title} does not support passthrough termination for Gateway API. Passthrough termination provides direct traffic encryption from the client to the service, and is only supported in traditional {product-title} routes. | ||
| `HTTPRoute` CRs do not support passthrough termination. To forward TLS traffic that the backend terminates, use a `TLSRoute` CR with a TLS passthrough listener. `TLSRoute` is the only Gateway API route kind that supports passthrough. For more information, see xref:routing-tls-requests-to-services.adoc#routing-tls-requests-to-services[Route TLS requests to services]. |
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.NoXrefInModules: Do not include xrefs in modules, only assemblies (exception: release notes modules).
| [NOTE] | ||
| ==== | ||
| {product-title} does not support passthrough termination for Gateway API. Passthrough termination provides direct traffic encryption from the client to the service, and is only supported in traditional {product-title} routes. | ||
| `HTTPRoute` CRs do not support passthrough termination. To forward TLS traffic that the backend terminates, use a `TLSRoute` CR with a TLS passthrough listener. `TLSRoute` is the only Gateway API route kind that supports passthrough. For more information, see xref:routing-tls-requests-to-services.adoc#routing-tls-requests-to-services[Route TLS requests to services]. |
There was a problem hiding this comment.
🤖 [error] AsciiDocDITA.ConceptLink: Move all links and cross references to Additional resources.
|
@jab-rh: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
4 participants
Version(s):
Issue:
Link to docs preview:
QE review:
Additional information: