Skip to content

Commit

Permalink
test: Test IPsec+VXLAN on 4.19
Browse files Browse the repository at this point in the history
The IPsec+VXLAN test was disabled on 4.19 long ago and never reenabled.
Since we now run with kube-proxy on 4.19, we can run it there.

We still can't run on GKE because we can't disable KPR there. See [1]
for details.

1 - #16597
Signed-off-by: Paul Chaignon <paul@cilium.io>
  • Loading branch information
pchaigno authored and errordeveloper committed Oct 12, 2021
1 parent d8a9ace commit faf5f4d
Showing 1 changed file with 5 additions and 8 deletions.
13 changes: 5 additions & 8 deletions test/k8sT/DatapathConfiguration.go
Original file line number Diff line number Diff line change
Expand Up @@ -195,14 +195,11 @@ var _ = Describe("K8sDatapathConfig", func() {
}
}

SkipItIf(helpers.RunsWithoutKubeProxy, "Check connectivity with transparent encryption and VXLAN encapsulation", func() {
// FIXME(brb) Currently, the test is broken with CI 4.19 setup. Run it on 4.19
// once we have kube-proxy disabled there.
if !helpers.RunsOnNetNextKernel() {
Skip("Skipping test because it is not running with the net-next kernel")
return
}

SkipItIf(func() bool {
// IPsec + encapsulation requires Linux 4.19.
// We also can't disable KPR on GKE at the moment (cf. #16597).
return helpers.RunsWithoutKubeProxy() || helpers.DoesNotRunOn419OrLaterKernel() || helpers.RunsOnGKE()
}, "Check connectivity with transparent encryption and VXLAN encapsulation", func() {
deploymentManager.Deploy(helpers.CiliumNamespace, IPSecSecret)
options := map[string]string{
"kubeProxyReplacement": "disabled",
Expand Down

0 comments on commit faf5f4d

Please sign in to comment.