Open andrewsykim opened 2 years ago
That seems like a bug, the builder should build the e2e binary, similar to https://github.com/kubernetes-sigs/kind/blob/main/hack/ci/e2e-k8s.sh
/help
@BenTheElder: This request has been marked as needing help from a contributor.
Please ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help
command.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the PR is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Hitting this issue in our job too: https://prow.k8s.io/log?container=test&id=1625285724066549760&job=pull-kubernetes-e2e-kind-kms. This is the command we're running: https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes/sig-auth/sig-auth-encryption-at-rest.yaml#L41-L52
/remove-lifecycle stale
Setting the
--use-built-binaries
flag for running tests doesn't seem to be working when using the kind deployer because the kind node image builder doesn't bundle the e2e.test binary.I wasn't sure if this was expected behavior but being able to run a single command to build a kind node image, start the cluster, and then run tests would be useful: