Open dylanscott opened 6 years ago
We also got this problem and fixed it with adding a ,
.
Solution
TARGETS="10.0.0.0/29,10.0.0.8/29" ./install.sh
Verification To verify this approach: login the VM instance in the gcloud console (GCP > Compute Engine > VM instances > SSH) and run:
sudo iptables -L -t nat | grep "custom-iptables"
You should see:
MASQUERADE all -- anywhere 10.0.0.0/29 /* custom-iptables-1537539514: 10.0.0.0/29,10.0.0.8/29 */
MASQUERADE all -- anywhere 10.0.0.8/29 /* custom-iptables-1537539514: 10.0.0.0/29,10.0.0.8/29 */
I can also verify that the solution above works.
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
(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