Closed benarent closed 2 years ago
This is the config that the teleport-cluster
Helm chart uses when proxyListenerMode: multiplex
is set:
version: v2
teleport:
log:
severity: INFO
output: stderr
format:
output: text
extra_fields: ["timestamp","level","component","caller"]
auth_service:
enabled: true
cluster_name: teleport.example.com
authentication:
type: local
second_factor: on
webauthn:
rp_id: teleport.example.com
proxy_listener_mode: multiplex
kubernetes_service:
enabled: true
listen_addr: 0.0.0.0:443
kube_cluster_name: teleport.example.com
proxy_service:
public_addr: 'teleport.example.com:443'
enabled: true
ssh_service:
enabled: false
Here's the matching teleport-kube-agent
config:
teleport:
auth_token: "token-goes-here"
auth_servers: ["teleport.example.com:443"]
log:
severity: INFO
output: stderr
format:
output: text
extra_fields: ["timestamp","level","component","caller"]
kubernetes_service:
enabled: true
kube_cluster_name: test-kube-cluster
app_service:
enabled: false
db_service:
enabled: false
auth_service:
enabled: false
ssh_service:
enabled: false
proxy_service:
enabled: false
I'm not sure what fixed this, but I made a few changes.
PROXY_ADDR=teleportvm.dkl8bje9lxmn.instruqt.io
-> PROXY_ADDR=teleportvm.dkl8bje9lxmn.instruqt.io:443
Description
What happened: Our Instruqt Kubernetes demo is broken as the Helm Kube agents isn't able to connection. This ticket has the teleport.yaml and debug log associated with it.
teleport.yaml
Adding Helm Chart
Debug Log from Kubernetes
Version: Teleport 9.0.3