From 166fdd105fde38b298f9917226a53786a1d51c7b Mon Sep 17 00:00:00 2001 From: hc-github-team-consul-core Date: Fri, 3 Feb 2023 17:04:38 -0600 Subject: [PATCH] backport of commit 124f625eaf25c3c00f4ae073afb8bf03446c2172 (#16151) Co-authored-by: Ashwin Venkatesh --- website/content/docs/k8s/annotations-and-labels.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/website/content/docs/k8s/annotations-and-labels.mdx b/website/content/docs/k8s/annotations-and-labels.mdx index 63b407fb15..3be0d59fe4 100644 --- a/website/content/docs/k8s/annotations-and-labels.mdx +++ b/website/content/docs/k8s/annotations-and-labels.mdx @@ -50,6 +50,10 @@ The following Kubernetes resource annotations could be used on a pod to control list of additional user IDs to exclude from traffic redirection when running in transparent proxy mode. +- `consul.hashicorp.com/use-proxy-health-check` - It this is set to `true`, it configures + a readiness endpoint on Consul sidecar proxy and queries the proxy instead of the proxy's inbound port which + forwards the request to the application. + - `consul.hashicorp.com/connect-service` - For pods that accept inbound connections, this specifies the name of the service that is being served. This defaults to the name of the Kubernetes service associated with the pod. @@ -81,7 +85,7 @@ The following Kubernetes resource annotations could be used on a pod to control ``` - Namespace (requires Consul Enterprise 1.7+): Upstream services may be running in a different namespace. Place - the upstream namespace after the service name. For additional details about configuring the injector, refer to + the upstream namespace after the service name. For additional details about configuring the injector, refer to [Consul Enterprise Namespaces](#consul-enterprise-namespaces) . ```yaml