Bug Report

General Information

• Environment description (GKE, VM-Kubeadm, vagrant-dev-env, minikube, microk8s, ...): k3s
• Kernel version (run uname -a): Linux thunderbird 6.6.36-1-lts #1 SMP PREEMPT_DYNAMIC Thu, 27 Jun 2024 12:26:27 +0000 x86_64 GNU/Linux
• Orchestration system version in use (e.g. kubectl version, ...)

Client Version: v1.30.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.29.6+k3s1

• Helm Version: version.BuildInfo{Version:"v3.15.2", GitCommit:"1a500d5625419a524fdae4b33de351cc4f58ec35", GitTreeState:"clean", GoVersion:"go1.22.4"}
• Link to relevant artifacts (policies, deployments scripts, ...): NA
• Target containers/pods: NA

To Reproduce

1. Setup a k8s cluster
2. Run the command: helm upgrade --install kubearmor kubearmor/kubearmor -n kubearmor --create-namespace
3. Error occurs

Release "kubearmor" does not exist. Installing it now.
Error: 1 error occurred:
        * ConfigMap in version "v1" cannot be handled as a ConfigMap: json: cannot unmarshal bool into Go struct field ConfigMap.data of type string

Expected behavior

KubeArmor Helm chart is deployed without any error

Release "kubearmor" does not exist. Installing it now.
NAME: kubearmor
LAST DEPLOYED: Wed Jul  3 13:09:24 2024
NAMESPACE: kubearmor
STATUS: deployed
REVISION: 1
TEST SUITE: None

Why is this happening?
ConfigMaps are supposed to handle map[string]string. In a recent merge, more field were added such as alertThrottling, maxAlertPerSec, throttleSec. The value for these fields are not string but boolean and ints. Hence the ConfigMap cannot be parsed