You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if this was actually causing any problems but I noticed the logs for the k8s-custom-iptables pods had errors every time the configuration was being printed after I installed it with 2 CIDR ranges. I ran
TARGETS="10.0.0.0/29 10.0.0.8/29" ./install.sh
(These were the two ranges printed out by two Cloud Memorystore instances - I was following this documentation). In the logs I was getting:
This went away after I reconfigured to combine the blocks into 10.0.0.0/28
The text was updated successfully, but these errors were encountered:
The README was showing a space-separated list of IP ranges in `TARGETS` or in `nat.rules`, which does not work and causes issue bowei#4 . Instead, the correct solution is to use a comma-separated list. This commit updates the README accordingly.
I don't know if this was actually causing any problems but I noticed the logs for the k8s-custom-iptables pods had errors every time the configuration was being printed after I installed it with 2 CIDR ranges. I ran
TARGETS="10.0.0.0/29 10.0.0.8/29" ./install.sh
(These were the two ranges printed out by two Cloud Memorystore instances - I was following this documentation). In the logs I was getting:
This went away after I reconfigured to combine the blocks into
10.0.0.0/28
The text was updated successfully, but these errors were encountered: