Carlos R.F.

This may be a security bug. I found this issue while researching it for another project. Adding a specific SELinux policy is just a last resort workaround. Fixing the linking...

See the `source` ip in the `smokeping_prober.yaml` file. It may be struggling with the routing because of it. Try commenting it out. ``` # source: 127.0.1.1 # Souce IP address...

@SuperQ , do you have any specific concern about the approach? I may be able to look into it. This is not an uncommon solution in Unix, but I noticed...

While dealing with another program, I thought of something. It would be best if the HUP signal would try to reload the config, and if it fails, keep using the...

I also included a commit for `/-/healthy` and `/-/reload`

Looking into it and it seems that it will be a significant refactor for little gain since the workaround is just restarting the process. I'll close this issue.

@SuperQ , I was just going the route of getting there programmatically by refreshing the actual variables. It will definitely require a good amount of shuffling around to keep the...

The operator also generates tons of repetitive logs This logs is constant: `{"level":"info","ts":1724084554.4051137,"caller":"controller/cluster.go:579","msg":"Config CR Status Updated Successfully"}` This is how many of those were generated in 3 days of the...

The controller is supposed to have the `--zap-log-level` flag: https://github.com/kubearmor/KubeArmor/blob/63534cad71635f574aee84275c814175e183f23a/pkg/KubeArmorController/main.go#L55 https://pkg.go.dev/sigs.k8s.io/controller-runtime/pkg/log/zap#Options.BindFlags For the operator and the snitch, I'm providing the PR below:

I see that it is being tracked here already: https://bitbucket.org/pl_shibby/tomato-arm/issues/184/apparently-wpa2-protocol-is-vulnerable-to.