Open fraenkel opened 3 years ago
Could you please share the full Helm command that you used to install the chart?
helm install teleport-kube-agent . --create-namespace --namespace teleport --set proxyAddr=xxx.yyy.zzz --set authToken=akubetoken --set kubeClusterName=testcluster
Does your proxyAddr
contain a port? It should have :3080
on the end to point to a proxy, or maybe :443
if you're running behind a load balancer.
Adding 443 fixed it... guess I did it and forgot that I did.
@awly Maybe we should consider making the proxy part of this error more obvious?
Yeah, the message should not hide the underlying error (connection refused) and should suggest checking the port in auth_servers
Description
Last week the chart was working fine. But this week any new deployment fails.
What happened:
The log contains
What you expected to happen: Success
How to reproduce it (as minimally and precisely as possible):
Environment
Teleport version (use
teleport version
): 5.1.0OS (e.g. from
/etc/os-release
): EKSWhere are you running Teleport? (e.g. AWS, GCP, Dedicated Hardware): AWS
Relevant Debug Logs If Applicable