karmor probe missing node related infos

[kranurag7]

karmor probe is missing node related information on a fresh instance.

To Reproduce:

On a fresh EC2 instance, when you run karmor probe then you get the following result.

$ karmor probe

Found KubeArmor running in Kubernetes

Daemonset :
Deployments :
 	kubearmor-relay              	Desired: 1	Ready: 1	Available: 1	
 	kubearmor-policy-manager     	Desired: 1	Ready: 1	Available: 1	
 	kubearmor-host-policy-manager	Desired: 1	Ready: 1	Available: 1	
 	kubearmor-annotation-manager 	Desired: 1	Ready: 1	Available: 1	
Containers :
 	kubearmor-relay-6fddb8865b-qr4pw              	Running: 1	Image Version: kubearmor/kubearmor-relay-server:latest  	
 	kubearmor-policy-manager-cb9dbc668-4jf52      	Running: 2	Image Version: gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0	
 	kubearmor-host-policy-manager-756b46d87c-645xk	Running: 2	Image Version: gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0	
 	kubearmor-annotation-manager-7fc8d9b964-ddh55 	Running: 2	Image Version: gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0	
 	kubearmor-dft65                               	Running: 1	Image Version: kubearmor/kubearmor:stable               	
Node 1 :
2023/03/25 09:38:04 an error occured when parsing file readObjectStart: expect { or n, but found , error found in #0 byte of ...||..., bigger context ...||...
2023/03/25 09:38:04 an error occured when printing output readObjectStart: expect { or n, but found , error found in #0 byte of ...||..., bigger context ...||...
2023/03/25 09:38:04 error occured when probing kubearmor nodes readObjectStart: expect { or n, but found , error found in #0 byte of ...||..., bigger context ...||...
Armored Up pods :
+-----------+------+--------+
| NAMESPACE | NAME | POLICY |
+-----------+------+--------+
+-----------+------+--------+

$ karmor version
karmor version 0.12.4 linux/amd64 BuildDate=2023-03-07T17:32:40Z
current version is the latest
kubearmor image (running) version kubearmor/kubearmor:stable

attached screenshot