EXTERNAL-IP not showing up on kubectl get nodes -o wide

[liszca]

After a lot of trying I setup keepalived to have a floating IP.

Adding this IP in kubectl edit svc traefik -n kube-system like this:

spec:
  allocateLoadBalancerNodePorts: true
  clusterIP: 10.43.142.208
  clusterIPs:
  - 10.43.142.208
  externalIPs:
  - 192.168.1.30

Sadly it doesn't show up when running kubectl get nodes -o wide.

For the whoami app its already working correct but who knows in which problems I might run later ...

[brandond]

Why would you expect the traefik service's ClusterIP show up as a node ExternalIP? These things are in no way related.

Did you want to set node-external-ip in the K3s config?

Please read the documentation: https://docs.k3s.io/cli/agent#networking

If you are using some other LB controller to manage a floating VIP for a LoadBalancer service, that STILL would not show up as a node IP.

[liszca]

Why would you expect the traefik service's ClusterIP show up as a node ExternalIP? These things are in no way related.

Keepalived manages the floating IP 192.168.1.30.
My nodes have 192.168.1.3{1..3}.
So my expectation was when I set the secondary IP Address from keepalived that it will show up as "EXTERNAL_IP".

Would you say it does matter from a NAT perspective to not have this "EXTERNAL-IP" showing up in kubectl get nodes?

[brandond]

Kubernetes knows nothing about any floating VIPs you have configured on your host, outside of Kubernetes.

"External IPs" are public IPs assigned to the node. Normally this would be in an environment like EC2 or GCS, where the interface on the host has a private "internal IP", and then is assigned a publicly routable "external IP" address that it can be reached at from the internet.

If you want floating IPs that are integrated into Kubernetes, use one of the Kubernetes LB controllers that I previously mentioned.