From 65d990533503600f789d08e70a95eba9926ea16c Mon Sep 17 00:00:00 2001 From: Husni Alhamdani Date: Wed, 20 Dec 2023 16:08:39 +0100 Subject: [PATCH] update protocol-selection notes (#14359) Signed-off-by: Husni Alhamdani --- .../traffic-management/protocol-selection/index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/en/docs/ops/configuration/traffic-management/protocol-selection/index.md b/content/en/docs/ops/configuration/traffic-management/protocol-selection/index.md index 44582e37ed..61718a9283 100644 --- a/content/en/docs/ops/configuration/traffic-management/protocol-selection/index.md +++ b/content/en/docs/ops/configuration/traffic-management/protocol-selection/index.md @@ -35,6 +35,8 @@ This can be configured in two ways: - By the name of the port: `name: [-]`. - In Kubernetes 1.18+, by the `appProtocol` field: `appProtocol: `. +If both are defined, `appProtocol` takes precedence over the port name. + Note that behavior at the Gateway differs in some cases as the gateway can terminate TLS and the protocol can be negotiated. The following protocols are supported: