Problem Definition

Given the deprecation of dockershim in Kubernetes and the continuous work in supporting Kubernetes for Windows ( with containerd ), there is a clear need to improve coverage in validation for containerd on Windows.

There are a number of areas that need attention both in terms of infrastructure & test coverage:

1. Setup periodic test runs & display results ( i.e testgrid or similar ).
2. Run tests on multiple Windows versions

The first two goals will offer any user a full picture of the status of containerd on Windows for most of the possible configurations ( i.e Windows 1903 & containerd v1.3 etc. ).

3. Enable cri-integration tests on Windows
4. Extend current test suite with tests for Windows specific features

Focusing on the infrastructure needed for expanding test coverage on Windows, there are a few alternatives in place:

1. Expanding current CI setup in containerd/containerd that uses github actions.

   • PROS: already in the current workflow
   • CONS:
     • it might be a hassle to coordinate & set up credentials for external infrastructure ( Azure VMs )
     • visualising results is less than ideal

2. Setting periodic jobs via K8s Prow

   • PROS:
     • given work done in sig-windows to ensure Windows coverage, Prow is already set up with appropriate credentials for any infrastructure needed.
     • displaying results via testgrid is trivial
     • precedent for this exists, although not currently maintained ( https://testgrid.k8s.io/sig-node-containerd#cri-validation-windows )
   • CONS:
     • needs coordination and approval from K8s infra maintainers.