Sean Gilhooly

Based on some advice provided in this slack thread: https://datawire-oss.slack.com/archives/CAUBBJSQZ/p1661549637194529 That thread, which describes this problem pretty much exactly except on a GCP cluster, includes a reference to some GCP...

I restarted the `traffic-manager` deployment (to restart the log file clean). I then ran ```shell telepresence connect telepresence list telepresence intercept notify --port 9190 --env-file tele-notify.env ``` When I remove...

@thallgren: I would have thought that the mutating trigger would trigger after something has been mutated. But I don't see any activity in Kubernetes of any mutations -- of course...

I did notice today that running the telepresence intercept command causes some activity on the deployment I'm trying to intercept. Basically, it re-deploys the workload as if it did a...

I've pretty much hit a dead end here. I don't know what additional information to gather, what else to try, or where else to look. It seems like something here...

@ipeychev : Thanks for the tip but this was the first thing we looked into when we ran into this issue (after hearing other's success with it). But, on AWS/EKS...

I get the same outcome on 2.7.6: The logs have a small bit of additional entries but otherwise the result is the same: ##### Command: ``` $> telepresence version Client:...

@cindymullins-dw: thanks for looking into it. I upgraded to the latest telepresence version and tried again to gather the information you requested. I don't see any complaints or interesting info...

See also #2727

Happy to report that after upgrading to version `v2.9.2` this problem seems to have been fixed. Intercepting a service was successful (although I had a follow on problem with getting...