## Issue - Currently `kube-system` is hard coded to prevent `kube-system` pods from running in Edera Protect. - This isn't a hard requirement, and should be configurable. - We should also allow end users to determine which Kubernetes Namespaces should be managed. ## Solution - Create a way to allow end users to either: - Define namespaces that protect-webhook should mutate - Define namespaces that protect-webhook should not mutate