This message was deleted.
# k3s
a
This message was deleted.
n
The services IPs themselves are seemingly being brought up on IP addresses that flannel clearly doesn't have an associated interface for, which is why I believe it's routing out through the default route... 10.46.0.0/24 for example on a node as part of a 10.46.0.0/16 pod CIDR, but the services IPs are 10.48.128.0/24.
If I added IPs on the node for the services IP range, then bounced the pods/services, would that then create the required routes to stop it routing out via default route? I mean, technically a services IP is attached to a networking rule somewhere...