Flannel layer not properly indicating when the subnet has changed

[Tim Van Steenburgh]

Opened by lazypower on 2016-10-01 05:03:52+00:00 at https://github.com/juju-solutions/charm-flannel/issues/14

------------------------------------------------------------

As flannel leases expire and new leases emerge, it becomes important to signal to consuming layers this has happened.
In the instance that I caught this, the docker daemon has an incorrect BIP after flannel has updated its service. this is causing kubernetes containers to run and have reachability to the outside world on an unrouteable address, however any cross pod communication or even communication from the master to the worker node is impossible.