Auto terminate Log Watcher once disconnected from KubeArmor

[daemon1024]

We currently don't terminate our log watchers once we get an EOF from KubeArmor, We need to manually send a SIGKILL or any other relevant signal to stop the process. We should auto exit the watcher and terminate the process once we receive this.

Hi, If it is the first time that you contribute to KubeArmor, follow these steps: Write a comment in this issue thread to let other possible contributors know that you are working on this bug. For eg : Hey all, I would like to work on this issue., checkout Contributing Guide :fire::sparkles: and feel free to ask anything related to this issue in this thread or on our slack channel ✌🏽

[s1ntaxe770r]

@daemon1024 I'll be taking this one

[pk-218]

Hi @daemon1024, I am able to reproduce the issue.

Steps I followed -

1. Installed karmor CLI
2. Run karmor install to install KubeArmor to local K3s cluster
3. Run wordpress-mysql microservice example as given in the docs.
4. Run kubectl -n wordpress-mysql exec -it wordpress-c4bf5b44b-lvkbl -- bash -c apt to trigger the ksp-wordpress-block-process KubeArmorSecurityPolicy
5. Run karmor uninstall to remove KubeArmor from the cluster and cause an error.
6. Output on terminal is obtained as - But the log client doesn't exit.

Can you assign this issue to me?

[daemon1024]

@pk-218 Thanks for taking it up, I see you already have an understanding of the issue but do lemme know if you need some help.