-
-
Notifications
You must be signed in to change notification settings - Fork 377
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
Add support for IPv6 addresses #398
Comments
Hi, have you tried --host instead of --ip? |
With --host I get the same error. I also tried --host with the |
I would be also interested in this. Most of VPS servers are quite cheaper when paying for IPv6 only |
I have no idea on the matter because I don't know much about the ssh library in go, but in a quick search I found this: kubernetes/minikube#625 and kubernetes/minikube#6110 they used to solve the same error in minikube |
Thanks for your interest @Charlio99 How cheap is your IPv6-only VPS? DO and Scaleway have VMs for 3-5 EUR/USD/mo. Is it cheaper than that? And is that the only driver here? |
Hello @alexellis, The price difference it’s 1,7EUR/mo in the 1vCPU 2GB RAM config, the thing is that if I spin up 3 clusters with 3 workers 1 cp each, it’s 20EUR/month I could be having almost 2 clusters more for that. Given that the main purpose of k3sup is to quickly spin up a k3s cluster, I think this is the ideal scenario. I would be willing to help implement it but I never used go before. |
I'm not in the position to test right now, since I fully changed my k8s server setup to harvester/rancher, rather than Windows+hyperv/multipass/k3sup, but I didn't test back then if ipv6 worked if you put square brackets around the address, similar to how you go to ipv6 addresses in the browser. @Charlio99 , could you test that? |
I tried that also, I did some more debugging today and it seems that github.com is a non IPv6 domain, so when get.k3s.io tried to fetch the last version, it can't... $ nslookup github.com
Server: 2606:4700:4700::1111
Address: 2606:4700:4700::1111#53
Non-authoritative answer:
Name: github.com
Address: 140.82.121.4 |
I found a way around, I've created this PR, it's a simple change to the docs explaining how to do it, feel free to edit anything you want. |
Great work! |
Why do you need this?
My node only has a reachable IPv6 address, so I tried to use
k3sup
with the following command:Expected Behaviour
I expect this to work the same way as for an IPv4 address
Current Behaviour
I get the following output:
Possible Solution
Add a
-6
flag for when the user wants to provide an IPv6 address. In such cases it might also be needed to specify the network adapter, like<IPv6>%eth0
. This seems to be the case forssh
, but not forping
, so you'd have to check if you need this.Steps to Reproduce
k3sup install --context <cluster context> --user <vm user> --ip <IPv6>
(with everything between <> filled in ofc.)Your Environment
What OS or type or VM are you using for your cluster? Where is it hosted? (for
k3sup install/join
):Operating System and version (e.g. Linux, Windows, MacOS):
Do you want to work on this?
Subject to design approval, are you willing to work on a Pull Request for this issue or feature request?
The text was updated successfully, but these errors were encountered: