CRI conformance tests

[xibz]

The runtime should be CRI conformant. To verify that the runtime is we need to run a set of tests to ensure this provided by containerd, ie CRI validation tests, CRI e2e (end to end) tests.

The validation tests should be implemented first due to e2e tests taking a long amount of time due to if something doesn't work, it'll timeout in 2 minutes for each test.

CRI Validation Test Issues:
#90 #91 #92 #93 #94 #95 #96 #97 #98 #99 #100 #101 #102 #103

[kzys]

Note that firecracker-contained binary we built is currently not having cri plugin, whereas containerd includes the plugin by default.

Building cri with firecracker-containerd should be possible, but it would add a bunch of "replace" directives on our go.mod, due to the way Kubernetes manages Go packages.

[alexandrevilain]

Hi @kzys !

Containerd is now supporting go modules (containerd/containerd#4760) and cri has been moved to containerd's main repo (https://github.com/containerd/containerd/tree/master/pkg/cri).

It think that we can work back on this issue.

Would you like to update #255 ? Or I can create a new one if you don't have time to work on it :)

[acpana]

@kzys is there an opportunity for us to resume work here? Or is this issue complete via #255 ?