Policy Reporter Targets as CRDs

[mveitas]

Currently all configuration for targets such as email, slack, etc are all done in a central location. This requires teams make a contribution to the main policy-reporter configuration and deploy the changes.

Creating a CRD that describes a target would allow teams to manage their notifications in a self-service manner. An example below:

apiVersion: kyverno.io/v1alpha1
kind: PolicyReporterTarget
spec:
   slack:
      webhook: "https://hooks.slack.com/services/123..."
      skipExistingOnStartup: true
      filter:
         namespaces:
            include: ["team-a-*"]
         priorities:
            exclude: ["info", "debug"]
         policies:
            include: ["require-*"]

Centralized configuration of SMTP server configuration would be kept within the core configuration for the Policy Reporter

[fjogeleit]

Hey, thanks for your feedback.

It would make sense to offer this kind of flexibility.

My current focus is the new UI and cleanup of the current codebase. This requires most of my time right now. When this is finished I will think about the offering of CRDs to provide runtime configurations.

[mveitas]

If this is not something that is on your the immediate radar, I might get it started. Email reporting is the big thing that I want to be able to tackle as this is something that teams are looking for to periodically get a summary of any policy violations

[JimBugwadia]

@mveitas - the plan is to eventually move all configurations to CRDs. This work has not been committed to a release, so contributions are welcome! A brief KDP would be great to get the process started.

[mveitas]

With 50 or so teams running in our Kubernetes clusters, we want to allow teams to define the configuration for their email reports first and avoid having to deploy the policy reporter to update a team's configuration. We have some centrally managed metadata about teams that has Slack channels, email, etc that would drive creation of these CRDs as part of our platform. I'll create a separate issue to extraction of the email configuration along with a KDP