Namespace monitoring overly aggresive in reporting failures

[gnunn1]

Currently the namespace check causes Cerberus to return a False status on any pod failing even if that pod is part of a multi-pod deployment. For example, one of my kube api pods got briefly recyled for some reason triggering the false flag even though the other two pods were up and from a user perspective the cluster was operational.

Are there any options to tune this behavior with regards to the namespace checking to tolerate some failures without reporting a False signal?