Open mattfarina opened 2 years ago
As has been pointed out on Slack, the logs are perfectly normal. /proc/sys/net/ipv4/ip_forward
cannot be changed, but as the lines below show, it is already set to the desired value (1
), so the error is benign.
After digging into this more, it may be me personally that's having the problem. More to follow.
The gist is that I have rules in iptables not from Kubernetes or containerd within Rancher Desktop for ports 80 and 443. The LoadBalancer is listening everywhere but localhost. It appears the issue is with these rules I need to track down.