From 54221e4dbb2e47b14491fdcdd1857db1671af90a Mon Sep 17 00:00:00 2001 From: Helene Durand Date: Fri, 28 Jun 2024 08:38:13 +0200 Subject: [PATCH] DOC/MINOR: In TCP CR doc, explain that the mode is forced to tcp --- documentation/custom-resource-tcp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/custom-resource-tcp.md b/documentation/custom-resource-tcp.md index 3610e12c..b533a6b0 100644 --- a/documentation/custom-resource-tcp.md +++ b/documentation/custom-resource-tcp.md @@ -57,7 +57,7 @@ A `TCP` CR contains a list of TCP services definitions. Each of them has: - a `name` - a `frontend` section that contains: - - a `frontend`: any setting from client-native frontend model is allowed + - a `frontend`: any setting from client-native frontend model is allowed (**except the `mode` that is forced to `tcp`**) - a list of `binds`: any setting from client-native bind model is allowed - a `service` defintion that is an Kubernetes upstream Service/Port (the K8s Service has to be in the same namespace as the TCP CR is deployed)