telepresence
telepresence copied to clipboard
telepresenceio
Intercept Fail. Readiness probe failed: stat: can't stat '/tmp/agent/ready'
Describe the bug
I am trying to intercept using the following command:
telepresence intercept -n dev tenant-api-tele --port 9000:grpc -env-file ~/example-service-intercept.env
But receive the following error:
telepresence: error: rpc error: code = DeadlineExceeded desc = request timed out while waiting for agent tenant-api-tele.dev to arrive
When I check the pods, it creates the pod with the agent successfully, but there is a warning when I do a describe pod:
The error specifically is:
Readiness probe failed: stat: can't stat '/tmp/agent/ready': No such file or directory
I check connector.log, it doesn't seem to have any error message.
Expected behavior Can connect successfully with Intercept
Versions (please complete the following information):
-
Output of
telepresence version
-
Operating system of workstation running
telepresencecommands = Windows -
Kubernetes environment and Version [e.g. Minikube, bare metal, Google Kubernetes Engine] = AKS
Additional context
- AKS cluster has different IP subnet compared to my host machine. But I can run kubectl fine from my machine
- Using telepresence for Windows. I had to manually install the trafficmanager and sshfs-win manually
- port 9000 and grpc (port 9000 in cluster) are grpc endpoints
- AKS is within internal network; need a VPN
It was my error; forgot we had a network policy applied to the kubernetes. Adding the appropriate rules worked.
Actually, I can't seem to figure out the IP / Port to unblock. I tried it successfully by removing the network policy.
Is there a document somewhere I can refer to for it?
I am getting the same error while trying to implement readme
in my aks cluster.
Hi @leanalcabasa , Telepresence 2.7.6 has been released. We've love for users who encountered the "Deadline Exceeded error" to try it and let us know if any improvement, or if more information about the error is output.
