kubernetes/pkg/proxy/util
Dan Winship 463153fb7c Fix ContainsIPv4Loopback() to match its caller's behavior
ContainsIPv4Loopback() claimed that "::/0" contains IPv4 loopback IPs
(on the theory that listening on "::/0" will listen on "0.0.0.0/0" as
well and thus include IPv4 loopback). But its sole caller (the
iptables proxier) doesn't use listen() to accept connections, so this
theory was completely mistaken; if you passed, eg,
`--nodeport-addresses 192.168.0.0/0,::/0`, then it would not create
any rule that accepted nodeport connections on 127.0.0.1, but it would
nonetheless end up setting route_localnet=1 because
ContainsIPv4Loopback() claimed it needed to. Fix this.
2023-01-21 14:25:08 -05:00
..
iptables Local Traffic Detector: Add two new modes 2022-03-25 20:06:06 +01:00
testing reduce cpu usage of kube-proxy with iptables mode 2021-07-05 16:08:19 +08:00
endpoints_test.go proxy/iptables: Remove unnecessary /32 and /128 in iptables rules 2021-11-09 09:32:50 -05:00
endpoints.go proxy/iptables: Remove unnecessary /32 and /128 in iptables rules 2021-11-09 09:32:50 -05:00
network.go reduce cpu usage of kube-proxy with iptables mode 2021-07-05 16:08:19 +08:00
nodeport_addresses_test.go Fix ContainsIPv4Loopback() to match its caller's behavior 2023-01-21 14:25:08 -05:00
nodeport_addresses.go Fix ContainsIPv4Loopback() to match its caller's behavior 2023-01-21 14:25:08 -05:00
utils_test.go Move GetNodeAddresses() and ContainsIPv4Loopback() into a new file 2023-01-21 14:25:07 -05:00
utils.go Move GetNodeAddresses() and ContainsIPv4Loopback() into a new file 2023-01-21 14:25:07 -05:00