E2e, delete ServiceExport before Service
Since Globalnet internally uses kubeproxy iptable chain, if we delete
the serviceExport first, we will give Globalnet opportunity to remove
all iptable references ahead of kubeproxy. This will inturn reduce the
possibilities of flaky errors to some extent.
@@ -178,8 +178,8 @@ func verifyGlobalnetDatapathConnectivity(p tcp.ConnectivityTestParams, egressIPT
Expect(listenerPod.TerminationMessage).To(matchIP)
- p.Framework.DeleteService(p.ToCluster, service.Name)
p.Framework.DeleteServiceExport(p.ToCluster, service.Name)
+ p.Framework.DeleteService(p.ToCluster, service.Name)
p.Framework.DeletePod(p.ToCluster, listenerPod.Pod.Name, listenerPod.Pod.Namespace)
p.Framework.DeletePod(p.FromCluster, connectorPod.Pod.Name, connectorPod.Pod.Namespace)
}
