From 47015fdabbf74eab54f0139ef084da55322106d0 Mon Sep 17 00:00:00 2001 From: Charlie Kenney Date: Fri, 5 Mar 2021 14:31:15 -0500 Subject: [PATCH] update hostname-only-ingress annotation docs Co-authored-by: Tim Horner --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 27071b37..53637d92 100644 --- a/README.md +++ b/README.md @@ -55,7 +55,7 @@ Annotation (Suffix) | Values | Default | Description `check-passive` | [bool](#annotation-bool-values) | `false` | When `true`, `5xx` status codes will cause the health check to fail `preserve` | [bool](#annotation-bool-values) | `false` | When `true`, deleting a `LoadBalancer` service does not delete the underlying NodeBalancer. This will also prevent deletion of the former LoadBalancer when another one is specified with the `nodebalancer-id` annotation. `nodebalancer-id` | string | | The ID of the NodeBalancer to front the service. When not specified, a new NodeBalancer will be created. This can be configured on service creation or patching -`hostname-only-ingress` | [bool](#annotation-bool-values) | `false` | When `true`, the LoadBalancerStatus for the service will only contain the Hostname. This is useful for bypassing kube-proxy rerouting in-cluster requests originally to the external LoadBalancer to the service's constituent pod IPs. +`hostname-only-ingress` | [bool](#annotation-bool-values) | `false` | When `true`, the LoadBalancerStatus for the service will only contain the Hostname. This is useful for bypassing kube-proxy's rerouting of in-cluster requests originally intended for the external LoadBalancer to the service's constituent pod IPs. #### Deprecated Annotations