From 5a3526d0c2b440baecdcc1cdda7dd781a2de2b7f Mon Sep 17 00:00:00 2001 From: Sara Thomas Date: Mon, 21 Jun 2021 13:27:30 -0400 Subject: [PATCH] BZ1878685: Updates to Creating a route via Ingress for passthrough routes --- ...-ingress-creating-a-route-via-an-ingress.adoc | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/modules/nw-ingress-creating-a-route-via-an-ingress.adoc b/modules/nw-ingress-creating-a-route-via-an-ingress.adoc index b1d74451b8..96b8a9d43e 100644 --- a/modules/nw-ingress-creating-a-route-via-an-ingress.adoc +++ b/modules/nw-ingress-creating-a-route-via-an-ingress.adoc @@ -41,6 +41,22 @@ spec: as `Ingress` has no field for this. The accepted values are `edge`, `passthrough` and `reencrypt`. All other values are silently ignored. When unset, `edge` is used. +.. If you specify the `passthrough` value in the `route.openshift.io/termination` annotation, set `path` to `''` and `pathType` to `ImplementationSpecific` in the spec: ++ +[source,yaml] +---- + spec: + rules: + - host: www.example.com + http: + paths: + - path: '' + pathType: ImplementationSpecific + - backend: + serviceName: frontend + servicePort: 443 +---- + + [source,terminal] ----