Comment 11 for bug 1897115

I think I've found a workaround. In this specific case, assigning "global" IPs to flannel does the trick to avoid the RFC-1918 vs non RFC-1918 case. 133.X.X.X won over 100.64.0.0/20, but I don't know what happens if the real IP is 90.Y.Y.Y or something (no idea how Juju sorts and determine the main IP address).

In any case, I'm downgrading this to ~field-high since we have one possible workaround to keep going.

$ ip -br a
lo UNKNOWN 127.0.0.1/8 ::1/128
flannel.1 UNKNOWN 100.64.8.0/32 fe80::9c37:6eff:fe35:e8b7/64
eth0@if55 UP 133.X.X.X/26 fe80::216:3eff:fef5:bd0a/64

$ juju run --unit kubernetes-master/0 -- network-get kube-api-endpoint --ingress-address
133.X.X.X