-
-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hanging at INFO[0000] waiting for deployment to be ready #45
Comments
hey @mysterybear can you try running ktunnel with the verbose flag to see if we can catch additional details from the logs? |
Hi @omrikiei I was running with the verbose flag already! I tried next thing I could try is running the client and server aspects separately rather than using the expose shorthand I guess? I'll try that, pretty busy and did get a tunnel working with frp for my use case this time |
Hey @mysterybear, on your client logs, do you see the following log message? |
I think this is happening because of a time offset between your machine and the kubernetes node, I will start working on a fix - if you could verify it that would be great! |
Yes that is there, I just didn't include it, sorry for that!
There's a 1 hour time difference between me:
And the node:
|
Hi, jfyi: we were hit by the same issue reproduced on mac with timezone difference with v1.3.4, after updating to v1.3.7 the issue was not reproduced. Note: on ubuntu with v1.3.3 the issue is not present. Hope that helps, |
Hey @mysterybear, issue is resolved on v1.3.7, could you kindly confirm it works now? |
Yes, confirmed! Thanks again @omrikiei ! |
Image is v1.3.6
Kubernetes side, deployment/pod seems to start up just fine:
Edit: just tried with v1.3.3 also since I remember that working for sure last time I used this (It's me from #36 :D) issue persists just the same... I've checked I haven't got any lingering ktunnel resources server-side as well
Edit:
k logs
on the server pod shows:The text was updated successfully, but these errors were encountered: