From f9f3b18ce4376be013e2ef08d931531ba44e0c90 Mon Sep 17 00:00:00 2001 From: Bryan Boreham Date: Mon, 6 Mar 2017 17:30:13 +0000 Subject: [PATCH] Test whether non-weave ipsets get blown away --- test/840_weave_kube_3_test.sh | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/test/840_weave_kube_3_test.sh b/test/840_weave_kube_3_test.sh index 6a9e8db6..d206524e 100755 --- a/test/840_weave_kube_3_test.sh +++ b/test/840_weave_kube_3_test.sh @@ -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