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
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