1. Proposed title of this feature request

Add Policy Scope to include/exclude based on Kubernetes kind

2. What is the nature and description of the request?

Currently Policy Scope can only be restricted in the Restrict by scope and Exclude by scope based on cluster, namespace(s), and labels - including use of regular expressions.  Deployment collections have similar limitations for selection rules.

Customer wishes to allow additional control by setting inclusion and exclusion based on Kubernetes types.  Instead of applying policies to a generic "Deployment", filtering would allow additional options to specify Kubernetes types such as Deployment, StatefulSet, Job/CronJob, and non-Deployment such as ConfigMaps, Secrets for example.

3. Why does the customer need this? (List the business requirements here)

Customer requires a Label to exist on all application deployments.  Currently this will show violations for Jobs/CronJobs but the customer does not require the label to be included on Jobs/CronJobs.   By allowing the Policy scope to include/exclude based on kubernetes type the user will be able to control which kubernetes objects policies are applied and eliminate violations for objects that are acceptable to their business rules.. 

4. List any affected packages or components.

• Deployment Collections
• Policy Scope