Thomas Hallgren
Thomas Hallgren
@alon7 please do. We will try and figure it out and, if possible, solve the problem.
Seems you entered that key verbatim as `timeouts.helm`. It's a hierarchical name and you need to reflect that: ``` timeouts: helm: 60s ```
@alon7 are you using numeric ports, but not on headless services? If so, [this section](https://www.getambassador.io/docs/telepresence/latest/troubleshooting/#injected-init-container-doesnt-function-properly) in the docs might be helpful.
@PetrSilar the logs aren't produced with loglevel debug, so they don't contain any info that will help trace network issues. I suspect that your problem is that the cluster have...
@PetrSilar, please take a look at https://github.com/telepresenceio/telepresence/issues/2456#issuecomment-1065893583 regarding the `iptables` problem.
What exact Helm command did you use to install the traffic-manager? In particular, did you specify `--namespace ambassador`?
I'm trying to figure out why Telepresence would log the message "No existing Traffic Manager found in namespace ambassador". It does that when the embedded helm cannot find it. So,...
Yes, that ticket looks like a duplicate, @josecv?
The "umount" is there as a precaution, in case the sshfs doesn't umount correctly. The fact that it fails is usually OK. The fact that forwards are terminating just 0.1...
Did you try the workaround that we recommend in our troubleshooting guide? https://www.getambassador.io/docs/telepresence/latest/troubleshooting/#volume-mounts-are-not-working-on-macos