[release/1.7] prow: allow ENABLE_CRI_SANDBOXES to be configured#10801
Conversation
|
Skipping CI for Draft Pull Request. |
This change will enable the pull-containerd-node-e2e-1-7-sandboxed job to pass down configuration enabling CRI sandboxes in containerd 1.7. This is an optional CRI backend in 1.7 and will be the new backend in containerd 2.0. Corresponding containerd change: containerd/containerd#10801 Signed-off-by: Samuel Karp <[email protected]>
|
This will be testable once kubernetes/test-infra#33603 is merged. |
|
/test pull-containerd-node-e2e-1-7-sandboxed |
3bff4b5 to
e137924
Compare
|
/test pull-containerd-node-e2e-1-7-sandboxed |
The pull-containerd-node-e2e-1-7-sandboxed job will set ENABLE_CRI_SANDBOXES for containerd 1.7 and enable us to validate that the sbserver backend works with e2e tests. Signed-off-by: Samuel Karp <[email protected]>
e137924 to
633201a
Compare
|
/test pull-containerd-node-e2e-1-7-sandboxed |
|
Looks like I missed a bit in the first test-infra PR; kubernetes/test-infra#33606 should fix it. |
|
/test pull-containerd-node-e2e-1-7-sandboxed |
So, the sandboxed jobs for 1.7 were testing without sbserver till now. |
Yeah, the pull-containerd-node-e2e-1-7-sandboxed prow job wasn't working properly. Our GitHub actions workflows for containerd CI are working, though, so we have had testing there. |
633201a to
ae11176
Compare
|
/test pull-containerd-node-e2e-1-7-sandboxed |
|
/retest |
This change will enable the pull-containerd-node-e2e-1-7-sandboxed job to pass down configuration enabling CRI sandboxes in containerd 1.7. This is an optional CRI backend in 1.7 and will be the new backend in containerd 2.0. Corresponding containerd change: containerd/containerd#10801 Signed-off-by: Samuel Karp <[email protected]>
The pull-containerd-node-e2e-1-7-sandboxed job will set ENABLE_CRI_SANDBOXES for containerd 1.7 and enable us to validate that the sbserver backend works with e2e tests.