From d75003cd831893b9891a687565a1dd6c142eb48c Mon Sep 17 00:00:00 2001 From: Tobias Balle-Petersen Date: Thu, 28 Sep 2023 09:45:10 +0200 Subject: [PATCH] Add example of routing non HTTP TCP traffic with Helm Chart Having an example of how to use this feature in the values.yaml makes it clear how it is to be used. --- charts/ingress-nginx/values.yaml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/charts/ingress-nginx/values.yaml b/charts/ingress-nginx/values.yaml index 2541f268d..6ecf83c35 100644 --- a/charts/ingress-nginx/values.yaml +++ b/charts/ingress-nginx/values.yaml @@ -153,6 +153,8 @@ controller: # -- Allows customization of the configmap / nginx-configmap namespace; defaults to $(POD_NAMESPACE) configMapNamespace: "" tcp: + # -- Route TCP traffic on port 22 to port 2222 on a service in the cluster + # 22: some-namespace/some-service:2222 # -- Allows customization of the tcp-services-configmap; defaults to $(POD_NAMESPACE) configMapNamespace: "" # -- Annotations to be added to the tcp config configmap