Replies: 3 comments
-
Hi @migs35323 |
Beta Was this translation helpful? Give feedback.
-
hello @rbrtbnfgl i ONLY provided the external ip as mentioned in the doc, i didn't provide an internal IP, i assumed the k3s would take care of that automatically |
Beta Was this translation helpful? Give feedback.
-
This seems like more of a line of questioning than a bug, so converting to a discussion :) |
Beta Was this translation helpful? Give feedback.
-
Environmental Info:
K3s Version: 1.24.10
Node(s) CPU architecture, OS, and Version:
ubuntu 22
Cluster Configuration:
1 server 2 workers
Describe the bug:
hello, i was testing a new vps cluster and i come across this documentation: https://docs.k3s.io/installation/network-options#distributed-hybrid-or-multicloud-cluster
is it normal that the internal and external ip addresses are the same?
the nodes show having a flannel-wg interface..
i did install wireguard as instructed, do i need to create a wireguard interface or config ?
how do i can know flannel is indeed using wireguard and the packets are going trough wireguard?
Steps To Reproduce:
behavior:
the cluster assumes the external ip as the internal ip,
(meaning both private and public ip are the vps external ip)
i am not sure if this is the normal behavior, or it should assume a private network
Beta Was this translation helpful? Give feedback.
All reactions