manifests: ensure kube-bridge uses latest CIDR

This commit ensures that the kube-bridge uses the latest CIDR assigned
by the Kubernetes API, rather than defaulting to a previously assigned
CIDR.

xref:
* https://github.com/containernetworking/plugins/tree/master/plugins/main/bridge#network-configuration-reference
* https://github.com/cloudnativelabs/kube-router/issues/689

Signed-off-by: Lucas Servén Marín <lserven@gmail.com>

manifests/kilo-bootkube.yaml

@@ -16,6 +16,7 @@ data:
              "type":"bridge",
              "bridge":"kube-bridge",
              "isDefaultGateway":true,
+             "forceAddress":true,
              "ipam":{
                 "type":"host-local"
              }

manifests/kilo-k3s.yaml

@@ -16,6 +16,7 @@ data:
              "type":"bridge",
              "bridge":"kube-bridge",
              "isDefaultGateway":true,
+             "forceAddress":true,
              "ipam":{
                 "type":"host-local"
              }

manifests/kilo-kubeadm.yaml

@@ -16,6 +16,7 @@ data:
              "type":"bridge",
              "bridge":"kube-bridge",
              "isDefaultGateway":true,
+             "forceAddress":true,
              "ipam":{
                 "type":"host-local"
              }

manifests/kilo-typhoon.yaml

@@ -16,6 +16,7 @@ data:
              "type":"bridge",
              "bridge":"kube-bridge",
              "isDefaultGateway":true,
+             "forceAddress":true,
              "ipam":{
                 "type":"host-local"
              }