Joe Searcy

Would be nice if this could become a sort of pluggable interface allowing users to define the specific endpoint, a templates request, and expected response. If this is done, the...

Sounds good. Assigning to you @ilrudie . Reach out whenever you want to sync on this.

Looking through the Service test manifests, there are some that I'm not 100% sure what they're suppose to be testing, so this may require some additional cleanup once we get...

2 more options come to mind for me: - Add new policy contribution docs to a new file at `docs/policy-contrib.md` - Rename existing `docs/policies.md` to `docs/core-policy-description.md` and add new contrib...

Yeah, good point...contributing probably isn't what we want. It's more policy development/framework/requirements. I think you're on the right path, feel free to move forward. I think I'm ok with either...

This may be of use: https://github.com/dorny/paths-filter

Could also be additional metadata in the policy definition. This could potentially support both `includeNamespaces` and `excludeNamespaces` without requiring an API call or cache lookup.

In general, it's somewhat assumed that end-users can't manipulate the namespace resource itself, including labels/annotations. I'd love to be able to move away from that assumption, but since the Admission...

@ilrudie Circling back around on this idea, and maybe we can add to the policy metadata like this: ```rego policy_metadata = { # Set MagTape Policy Info "name": "policy-emptydir", "severity":...

Ok, this seems to be related to the multi-process configuration with Gunicorn. There are multiple processes with full copies of MagTape running per pod, therefore multiple metrics counters per pod....