Add GitHub Action for k8s node e2e tests #12028
Conversation
|
Skipping CI for Draft Pull Request. |
|
/test all |
5c7e014 to
6697cc8
Compare
ea480c3 to
ee61c53
Compare
|
/cc @BenTheElder |
|
@chrishenzie: GitHub didn't allow me to request PR reviews from the following users: BenTheElder. Note that only containerd members and repo collaborators can review this PR, and authors cannot review their own PRs. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
NOTE: You can view the test output by checking the E2E / Kubernetes Node action below. There may be some more configuration bits we need to borrow from the existing The main difference between this workflow and the existing Prow job is that we're skipping However the test failed whether the gate was enabled or disabled. Here's an example failure if you'd like to take a look. |
estesp
left a comment
There was a problem hiding this comment.
LGTM; looks like a solid starting point for migrating off prow
ee61c53 to
f21f77d
Compare
|
/hold |
Introduces a workflow to run Kubernetes node e2e tests against containerd pull requests. This is the first step in migrating containerd's CI off of the community-owned prow.k8s.io infrastructure. This new workflow is modeled after the existing presubmit job: https://github.com/kubernetes/test-infra/blob/master/config/jobs/containerd/containerd/containerd-presubmit-jobs.yaml Initially this workflow will not be required to pass on PRs. We can make it required later once it's proven to be stable. Signed-off-by: Chris Henzie <chrishenzie@google.com>
f21f77d to
b92e8b5
Compare
|
@chrishenzie thx for doing this! |
Introduces a new GitHub Actions workflow to run Kubernetes node e2e tests against containerd pull requests. This is the first step in migrating containerd's CI off of the community-owned prow.k8s.io infrastructure.
This new workflow is modeled after the existing presubmit job.
Initially this workflow will not be required to pass on PRs. We can make it required later once it's proven to be stable.
Part of #11486 (but doesn't fully fix it yet).