{{ message }}
This repository was archived by the owner on Aug 15, 2022. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 15, 2022. It is now read-only.
koding: make tunnelserver a part of open-source environment #8920
Description
Currently installing kd fails in open-source environments due to mismatched keys - klient tries to connect to t.koding.com with kite.key generated by user's key pair, which is not going to work.
Expected Behavior
KD should install successfully in open-source environment.
Current Behavior
KD does not install successfully in open-source environment.
Possible Solution
To make kd working in open-source environment we should:
- start tunnelserver with docker-compose
- pass tunnel-kite-url to kloud so it uses correct one for vagrant stacks
- adapt klient/install.sh to allow for overwriting -tunnel-kite-url
Steps to Reproduce (for bugs)
Related #8919.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Activity
rjeczalik commentedon Aug 31, 2016
/cc @leeola
rjeczalik commentedon Aug 31, 2016
Related https://koding-dev.slack.com/archives/general/p1472460267000030.
CRACKBOY commentedon Aug 31, 2016
thank you @rjeczalik for you help.
Klient is working and bound just on IPv6...
tcp6 0 0 :::56790 :::* LISTEN 11856/klient
rjeczalik commentedon Aug 31, 2016
@CRACKBOY The
::56790is another HTTP server of klient, the one that does TLS termination for web IDE communication. It is started regardless klient is able to get up or not.Your klient is trying to retry to establish kontrol connection with tunnelled endpoint. Until that happens it does not start the api server.
I will see whether I can improve it to start only for local serving (only for kd).
CRACKBOY commentedon Aug 31, 2016
ok @rjeczalik
here what happened:
after getting kite and kd installed, Kd trying to consulte 127.0.0.1:56789/kite which expected to be exposed by klient. but klient bound on 56789 on IPv6 as I said in the previews comment.
here, what happened exactly: http://pastebin.com/mS9Ugjim
rjeczalik commentedon Aug 31, 2016
@CRACKBOY Klient starts two servers:
Because of the problem described in this issue, the api server does not start and that's why it does not respond to
127.0.01:56789/kiterequests, which are used by KD as a healthcheck.This is roughly how it's supposed to work. :-)
CRACKBOY commentedon Aug 31, 2016
Very clear, Thank you @rjeczalik
JacerOmri commentedon Aug 31, 2016
We've been playing with the tunnel server binary for a while,
We know it communicates with Route53 and more, but we're stuck with 404 error.
Surely we're missing something, is there any docs about it so we could help?
rjeczalik commentedon Aug 31, 2016
@CRACKBOY @JacerOmri I did improve klient to not get stuck when it can't establish a tunnelled connection. Actually it was a bug fix, since we planned to do so long ago.
Could you please retry installing your KDs? You still won't be able to e.g. build vagrant stacks until this very issue is resolved, but you should be able to use kd.
dosire commentedon Sep 6, 2016
Also see https://gitlab.com/gitlab-org/omnibus-gitlab/issues/1528#note_14896051
sibblegp commentedon Sep 7, 2016
Gitlab considers this bug to be extremely important.
rjeczalik commentedon Sep 7, 2016
Prerequisite for this issue - #8965.
Although if someone hacks a quick fix - that is to add TUNNELURL to install-kd.sh and extend docker-compose with tunnelserver - it would also be an acceptable solution.
twk3 commentedon Sep 9, 2016
I'm also stuck with the 404 error when trying to run the tunnel. starting it with -debug doesn't give much more info.
twk3 commentedon Sep 10, 2016
using -nocname gets past the 404