-
Notifications
You must be signed in to change notification settings - Fork 131
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
Kilo ignores --port argument? #397
Comments
So I think this is actually due to both Kilo and Kubespan trying to use port 51820. I've set the I'm going to try and disable Kubespan to see if I can verify this is the issue, but I'm not sure why Kilo isn't respecting the port argument. EDIT: Confirmed by removing Kubespan. |
I have tested this again today and it seems to have worked without issue now that KubeSpan is disabled. I will try it with KubeSpan again to see if there's something strange going on. |
@absolutejam did you get confirmation? how did you try to set the |
Hey!
I'm looking to use Kilo to connect a couple of clusters and I'm testing it in a Proxmox environment using Talos linux at the moment.
I've deployed it to 2 separate clusters, but on both I see the error
address already in use
in the logs.I've also tried exec'ing into a node debug container and bringing up the
kilo0
interface and I get the same error (I assumed as much as the error points tonetlink
doing the same).Originally I thought this was because the nodes were all seemingly getting the same IP address in the Kilo subnet, but I've altered the DaemonSet so that it just schedules onto a single node now.
For reference, I'm running Talos Linux (With Kubespan enabled) and Cilium.
Node public IP range (both clusters):
192.168.0.1/24
This cluster's internal IP range:
10.1.5.0/24
This cluster's Pod range:
10.105.128.0/17
This cluster's Service range:
10.105.0.0/17
Here's how I'm running Kilo in the DaemonSet:
Here's a larger chunk of the logs from Kilo:
The text was updated successfully, but these errors were encountered: