Fix failures due to IP_FAMILIES change

This PR sets KIND_IP_FAMILY to align with the IP_FAMILY used in Sail Operator scripts. Since the order of IP families is not relevant for Sail Operator e2e tests, we do not require the IP_FAMILIES variable used upstream. Fixes: istio-ecosystem#558 Signed-off-by: Sridhar Gaddam <[email protected]>
sridhargaddam · Jan 16, 2025 · 31c7227 · 31c7227
1 parent ba24e34
commit 31c7227
Showing 1 changed file with 3 additions and 0 deletions.
diff --git a/tests/e2e/integ-suite-kind.sh b/tests/e2e/integ-suite-kind.sh
@@ -28,6 +28,9 @@ export KIND_REGISTRY_PORT="5000"
 export KIND_REGISTRY="localhost:${KIND_REGISTRY_PORT}"
 export DEFAULT_CLUSTER_YAML="${SCRIPTPATH}/config/default.yaml"
 export IP_FAMILY="${IP_FAMILY:-ipv4}"
+
+# See https://github.com/istio-ecosystem/sail-operator/issues/558
+export KIND_IP_FAMILY="${IP_FAMILY}"
 export ARTIFACTS="${ARTIFACTS:-$(mktemp -d)}"
 export MULTICLUSTER="${MULTICLUSTER:-false}"
 # Set variable to exclude kind clusters from kubectl annotations.