From ec9973b54bcd0f11825a7c6285063b890a9088bc Mon Sep 17 00:00:00 2001 From: Jonny Ervine Date: Sun, 10 Sep 2023 08:20:17 +0800 Subject: [PATCH] Use ingress --- teleport-cluster/values-home.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/teleport-cluster/values-home.yaml b/teleport-cluster/values-home.yaml index 626df7b..39847ed 100644 --- a/teleport-cluster/values-home.yaml +++ b/teleport-cluster/values-home.yaml @@ -147,7 +147,7 @@ authentication: # To use an ingress, set proxyListenerMode=multiplex, ingress.enabled=true and service.type=ClusterIP # # Possible values are 'separate' and 'multiplex' -proxyListenerMode: "separate" +proxyListenerMode: "multiplex" # Optional setting for configuring session recording. # See `session_recording` under https://goteleport.com/docs/setup/reference/config/#teleportyaml @@ -568,7 +568,7 @@ service: # Using an Ingress also requires that you use the `tsh` client to connect to Kubernetes clusters and databases behind Teleport. # See https://goteleport.com/docs/architecture/tls-routing/#working-with-layer-7-load-balancers-or-reverse-proxies-preview for details. ingress: - enabled: false + enabled: true # Setting suppressAutomaticWildcards to true will not automatically add *. as a hostname served # by the Ingress. This may be desirable if you don't use Teleport Application Access. suppressAutomaticWildcards: false