From d5315dd1b2ec87d5997e29483324e4f94c51d6c8 Mon Sep 17 00:00:00 2001 From: Lukasz Dziedziak Date: Wed, 29 Jan 2025 03:10:36 -0500 Subject: [PATCH] test(e2e): provide kubeconfig on kind cluster removal (#12695) ## Motivation We observed that during multizone tests, while all tests succeeded, the job occasionally failed with the following error: ``` failed to update kubeconfig: failed to lock config file: open /home/ubuntu/.kube/config.lock: file exists ``` After investigating the issue and reviewing similar cases, I came across a suggestion to provide a kubeconfig file. Reusing a specific kubeconfig file could help prevent this issue from occurring. ## Implementation information Provide kubeconfig file location on removal ## Supporting documentation xref: https://github.com/kubernetes-sigs/kind/issues/ 2008 Signed-off-by: Lukasz Dziedziak --- mk/kind.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mk/kind.mk b/mk/kind.mk index 9e7e0a93a95d..b7f6225adbb8 100644 --- a/mk/kind.mk +++ b/mk/kind.mk @@ -65,7 +65,7 @@ kind/wait: .PHONY: kind/stop kind/stop: kind/cleanup-docker-credentials - @$(KIND) delete cluster --name $(KIND_CLUSTER_NAME) + @$(KIND) delete cluster --kubeconfig $(KIND_KUBECONFIG) --name $(KIND_CLUSTER_NAME) @rm -f $(KUBECONFIG_DIR)/$(KIND_KUBECONFIG) .PHONY: kind/stop/all