reweave/weave
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Test whether non-weave ipsets get blown away

Browse Source
This commit is contained in:
Bryan Boreham authored and Marc Carré committed 2017-03-14 17:56:59 +00:00
1 parent dc2925263c
commit f9f3b18ce4
1 file changed
+7
Download Patch File Download Diff File Expand all files Collapse all files
test/840_weave_kube_3_test.sh
+7
View File
@@ -20,6 +20,10 @@ SUCCESS="6 established"
tear_down_kubeadm
# Make an ipset, so we can check it doesn't get wiped out by Weave Net
docker_on $HOST1 run --rm --privileged --net=host --entrypoint=/usr/sbin/ipset weaveworks/weave-npc create test_840_ipset bitmap:ip range 192.168.1.0/24 || true
docker_on $HOST1 run --rm --privileged --net=host --entrypoint=/usr/sbin/ipset weaveworks/weave-npc add test_840_ipset 192.168.1.11
run_on $HOST1 "sudo systemctl start kubelet && sudo kubeadm init --token=$TOKEN"
run_on $HOST2 "sudo systemctl start kubelet && sudo kubeadm join --token=$TOKEN $HOST1IP"
run_on $HOST3 "sudo systemctl start kubelet && sudo kubeadm join --token=$TOKEN $HOST1IP"
@@ -76,4 +80,7 @@ assert_raises wait_for_pods
tear_down_kubeadm
# Destroy our test ipset, and implicitly check it is still there
assert_raises "docker_on $HOST1 run --rm --privileged --net=host --entrypoint=/usr/sbin/ipset weaveworks/weave-npc destroy test_840_ipset"
end_suite