Connectivity issues with EKS cluster

[cmeans]

Hi,

We're using an older version of Telepresence. v2.14.4
This is to avoid onboarding confusion with requiring a Telepresence Cloud Account.

Initial connectivity was fine...this is our Staging cluster, and not used much, but we're testing consuming the prometheus metrics being emitted and have just configured datadog to scrape them via openmetrics.

The error encountered is:

telepresence intercept portfolio -n devx-688 --port 3002:80
Connected to context arn:aws:eks:us-east-2:030187089201:cluster/aws-oh-uat-staging (https://DA376CFC6A21FC400D2C755EB813D7F2.gr7.us-east-2.eks.amazonaws.com)
telepresence intercept: error: connector.CreateIntercept: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: Get "https://DA376CFC6A21FC400D2C755EB813D7F2.gr7.us-east-2.eks.amazonaws.com/api/v1/namespaces/ambassador/services/traffic-manager\": net/http: TLS handshake timeout"

See logs for details (29 errors found): "/home/cmeans/.cache/telepresence/logs/daemon.log"
See logs for details (24 errors found): "/home/cmeans/.cache/telepresence/logs/connector.log"
If you think you have encountered a bug, please run telepresence gather-logs and attach the telepresence_logs.zip to your github issue or create a new one: https://github.com/telepresenceio/telepresence/issues/new?template=Bug_report.md .

Detailed logs attached:
telepresence_logs.zip

Thanks!

[thallgren]

If you wish to avoid the onbording confusion, why not use the Open Source version of Telepresence? It's currently at version 2.21.3.

[cmeans]

My fault...missed that. Thanks @thallgren .