Skip to content

Commit

Permalink
Delete kind cluster after tests run.
Browse files Browse the repository at this point in the history
Inside a real Prow job it is better to clean up at runtime instead of leaving that to the Prow job cleanup code because the later sometimes times out.

Signed-off-by: Mucahit Kurt <mucahitkurt@gmail.com>
  • Loading branch information
mucahitkurt committed Nov 21, 2019
1 parent 4fcafec commit 1eaaaa1
Showing 1 changed file with 15 additions and 0 deletions.
15 changes: 15 additions & 0 deletions prow.sh
Original file line number Diff line number Diff line change
Expand Up @@ -580,6 +580,19 @@ EOF
export KUBECONFIG
}

# Deletes kind cluster inside a prow job
delete_cluster_inside_prow_job() {
# Inside a real Prow job it is better to clean up at runtime
# instead of leaving that to the Prow job cleanup code
# because the later sometimes times out (https://github.com/kubernetes-csi/csi-release-tools/issues/24#issuecomment-554765872).
if [ "$JOB_NAME" ]; then
if kind get clusters | grep -q csi-prow; then
run kind delete cluster --name=csi-prow || die "kind delete failed"
fi
unset KUBECONFIG
fi
}

# Looks for the deployment as specified by CSI_PROW_DEPLOYMENT and CSI_PROW_KUBERNETES_VERSION
# in the given directory.
find_deployment () {
Expand Down Expand Up @@ -1017,6 +1030,7 @@ main () {
fi
fi
fi
delete_cluster_inside_prow_job
fi

if tests_need_alpha_cluster && [ "${CSI_PROW_E2E_ALPHA_GATES}" ]; then
Expand Down Expand Up @@ -1047,6 +1061,7 @@ main () {
fi
fi
fi
delete_cluster_inside_prow_job
fi
fi

Expand Down

0 comments on commit 1eaaaa1

Please sign in to comment.