feat(network-chaos): Adding support for containerd/crio in network-chaos (#321)

Signed-off-by: shubhamchaudhary <shubham.chaudhary@mayadata.io>

charts/generic/pod-network-corruption/engine.yaml

@@ -36,4 +36,15 @@ spec:
               value: 'eth0'
               
             - name: TOTAL_CHAOS_DURATION
-              value: '60' # in seconds
+              value: '60' # in seconds
+
+            # provide the name of container runtime
+            # it supports docker, containerd, crio
+            # default to docker
+            - name: CONTAINER_RUNTIME
+              value: 'docker'
+
+            # provide the container runtime path
+            # applicable only for containerd and crio runtime
+            - name: CONTAINER_PATH
+              value: '/run/containerd/containerd.sock'

charts/generic/pod-network-corruption/experiment.yaml

@@ -61,7 +61,7 @@ spec:
       value: ''
 
     - name: LIB
-      value: 'pumba'
+      value: 'litmus'
 
     ## percentage of total pods to target
     - name: PODS_AFFECTED_PERC
@@ -69,5 +69,16 @@ spec:
 
     - name: TARGET_POD
       value: ''
+
+    # provide the name of container runtime
+    # it supports docker, containerd, crio
+    # default to docker
+    - name: CONTAINER_RUNTIME
+      value: 'docker'
+
+    # provide the container runtime path
+    # applicable only for containerd and crio runtime
+    - name: CONTAINER_PATH
+      value: '/run/containerd/containerd.sock'
     labels:
       name: pod-network-corruption