From 1b80aa6c523cea86685562eb18bf606a4f7e97c7 Mon Sep 17 00:00:00 2001 From: Denis Mishin Date: Wed, 12 Jan 2022 11:15:55 -0500 Subject: [PATCH] document service_proxy_upstream ingress annotation (#2915) --- docs/docs/k8s/ingress.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/docs/k8s/ingress.md b/docs/docs/k8s/ingress.md index f2f628768..a53c525a2 100644 --- a/docs/docs/k8s/ingress.md +++ b/docs/docs/k8s/ingress.md @@ -167,6 +167,7 @@ The remaining annotations are specific to or behave differently than they do whe | `ingress.pomerium.io/tls_downstream_client_ca_secret` | Name of Kubernetes `tls` Secret containing a [Client CA][client-certificate-authority] for validating downstream clients. | | `ingress.pomerium.io/secure_upstream` | When set to `"true"`, use `https` when connecting to the upstream endpoint. | | `ingress.pomerium.io/path_regex` | When set to `"true"` enables path regex matching. See the [Regular Expressions Path Matching](#regular-expressions-path-matching) section for more information. | +| `ingress.pomerium.io/service_proxy_upstream` | When set to `"true"` forces Pomerium to connect to upstreams through the k8s service proxy, and not individual endpoints.
This is useful when deploying Pomerium inside a service mesh. | ::: tip