From bb99ca974bc8cc6738fdeb30b0c908ae24d252da Mon Sep 17 00:00:00 2001 From: Cezary Zawadka Date: Fri, 7 Jul 2023 15:31:57 +0200 Subject: [PATCH] Update create-external-load-balancer.md describe Healcth check node port response add info about new response header in 1.28 https://github.com/kubernetes/kubernetes/pull/118999 This was discussed on SIG Network on 6th July 2023 --- .../create-external-load-balancer.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/content/en/docs/tasks/access-application-cluster/create-external-load-balancer.md b/content/en/docs/tasks/access-application-cluster/create-external-load-balancer.md index d0ac36881a915..76346cb1d8047 100644 --- a/content/en/docs/tasks/access-application-cluster/create-external-load-balancer.md +++ b/content/en/docs/tasks/access-application-cluster/create-external-load-balancer.md @@ -158,6 +158,21 @@ spec: ### Caveats and limitations when preserving source IPs +Health check node port serves HTTP traffic. The response body contains JSON service name, namespace and number +of local endpoints: + +```json +{ + "service": { + "namespace": "default", + "name": "example-service" + }, + "localEndpoints": 2 +} +``` + +Starting from kubernetes v1.28 number of local endpoints is returned also in response header `X-Load-Balancing-Endpoint-Weight`. + Load balancing services from some cloud providers do not let you configure different weights for each target. With each target weighted equally in terms of sending traffic to Nodes, external