Skip to content

Commit

Permalink
prow.sh: work around "kind build node-image" failure
Browse files Browse the repository at this point in the history
Kind 0.9.0 accesses the "bazel-out" directory with a relative path,
which only works when the command is invoked inside the Kubernetes
source code
directory (kubernetes-sigs/kind#1910).
  • Loading branch information
pohly committed Oct 27, 2020
1 parent 22c0395 commit 9a370ab
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion prow.sh
Original file line number Diff line number Diff line change
Expand Up @@ -558,7 +558,8 @@ start_cluster () {
git_clone_branch https://github.com/kubernetes/kubernetes "${CSI_PROW_WORK}/src/kubernetes" "$version" || die "checking out Kubernetes $version failed"

go_version="$(go_version_for_kubernetes "${CSI_PROW_WORK}/src/kubernetes" "$version")" || die "cannot proceed without knowing Go version for Kubernetes"
run_with_go "$go_version" kind build node-image --image csiprow/node:latest --type="$type" --kube-root "${CSI_PROW_WORK}/src/kubernetes" || die "'kind build node-image' failed"
# Changing into the Kubernetes source code directory is a workaround for https://github.com/kubernetes-sigs/kind/issues/1910
(cd "${CSI_PROW_WORK}/src/kubernetes" && run_with_go "$go_version" kind build node-image --image csiprow/node:latest --type="$type" --kube-root "${CSI_PROW_WORK}/src/kubernetes") || die "'kind build node-image' failed"
csi_prow_kind_have_kubernetes=true
fi
image="csiprow/node:latest"
Expand Down

0 comments on commit 9a370ab

Please sign in to comment.