nirmata_test.sh updated to include tests for containerd. README.md up…

…dated to demonstrate containerd and kafka-controller checks.

Signed-off-by: rootxrishabh <[email protected]>

nirmata_test/README.md

@@ -68,6 +68,7 @@ Testing SELinux
 ip_forward enabled
 bridge-nf-call-iptables enabled
 Docker is active
+Containerd is active
 Found nirmata-agent.service testing Nirmata agent
 Test Nirmata Agent
 Nirmata Agent is running
@@ -86,8 +87,11 @@ Testing Zookeeper pods
 zk-0 is zookeeper standalone
 Found One Zookeeper Pod.
 Testing Kafka pods
-Found Kafka Pod kafka-0   1/1   Running   2     3d17h
-Found One Kafka Pod.
+Found Kafka Pod kafka-0
+Testing Kafka controller pods
+kafka-0 API is healthy!
+Found Kafka Controller Pod kafka-controller-0
+kafka-controller-0 API is healthy!
 Test completed with warnings.
 return is 2
 ```

nirmata_test/nirmata_test.sh

@@ -903,6 +903,24 @@ else
   fi
 fi
 
+# tests for containerd
+if ! systemctl is-active containerd &>/dev/null ; then
+    warn 'Containerd service is not active? Maybe you are using some other CRI??'
+else
+    containerdVersion=$(containerd --version | awk '{print $3}')
+    if [[ $containerdVersion < 1.6.19 ]] ;then
+        warn 'Install containerd version 1.6.19 or later'
+    else
+        CONFIG_FILE="/etc/containerd/config.toml"
+        if grep -q 'SystemdCgroup = true' "$CONFIG_FILE"; then
+            good Containerd is active
+        else
+            warn "SystemdCgroup is not set to true in $CONFIG_FILE"
+        fi
+
+    fi
+fi
+
 #Customers often have time issues, which can cause cert issues.  Ex:cert is in future.
 if type chronyc &>/dev/null;then
   if chronyc activity |grep -q "^0 sources online";then