Use ingress
This commit is contained in:
parent
7f5d28679b
commit
ec9973b54b
@ -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 *.<clusterName> as a hostname served
|
||||
# by the Ingress. This may be desirable if you don't use Teleport Application Access.
|
||||
suppressAutomaticWildcards: false
|
||||
|
||||
Loading…
Reference in New Issue
Block a user