container-kill: Sending SIGTERM instead of SIGKILL when using CRIO runtime

[radudd]

I am trying to use container-kill experiment with OpenShift 4 which uses CRIO 1.19 as container runtime.

Checking in the code, this experiment is triggered by executing crictl stop container-id [1]
But looking then to the underlying terminated container, I see that its exit code is 143, i.e. it receives a SIGTERM, but not a SIGKILL.
However, if I try a manual test directly from the host and I add the --timeout=0 to the crictl stop command, the container will receive a SIGKILL, i.e its exit status will be 137.
Following PR should fix this issue: #306

Many thanks!

[1]

litmus-go/chaoslib/litmus/container-kill/helper/container-kill.go

Line 159 in e9ea060

cmd := exec.Command("crictl", "-i", endpoint, "-r", endpoint, "stop", string(containerID))

[ksatchit]

Thank you @radudd !

[radudd]

Many thanks for merging the PR #306.
Would it also be possible to backport it to versions 1.11 and 1.12? Thanks!