https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3s
a
This message was deleted.
c
Don't believe what netstat tells you, it's not bound to only tcp6. It is listening on all addresses for both ipv4 and ipv6. If you're having problems, this is not the root cause.
b
i'm having same issue the error i was getting is
Copy code
https: listen tcp x.x.x.x:6443: bind: cannot assign requested address
Copy code
curl -sfL <https://get.k3s.io> | sh -s - --bind-address ${PUBLIC_IP}
PUBLIC_IP is node external ip
c
do you have something else already listening on 6443?
b
no
it is binding when ip is 0.0.0.0 or node internal ip but when i try to bind node public ip it is giving error
c
Why are you trying to do that to begin with?
b
i was trying to create cluster and manage cluster with pulumi so , the kubeconfig in /etc/rancher/k3s/k3s.yaml is with localhost server that i cannot access cluster directly when i export and use with pulumi kubernetes
i can access cluster outside if i bind public ip in the beginning of cluster creation
c
Don’t do that! Just change the address in the k3s.yaml file.
You don’t need to change where it is listening, all you need to do is edit the file to point at your IP. This is covered in the docs.
b
but any idea why —bind-address is not working with public ip?
c
I don’t know. But you’re trying to solve the wrong problem.
b
i have seen in this blog
c
just leave it alone, and edit the k3s.yaml kubeconfig to change the server address.
b
okay thanks
29 Views
Open in Slack
PreviousNext
Powered by