kyverno: [BUG] A policy is being applied on pods created by Jobs even it is not defined in the policy

Software version numbers

• Kubernetes version: v1.21.5
• Kyverno version: v1.5.8

Describe the bug

When we create a policy to be applied on Pods and Pods created by DaemonSet, Deployment and StatefulSet controllers, e.g. require-pod-probes policy, the policy is still being applied on Pods created by Jobs or CronJobs. We expect that these Pods created by Jobs and Cronjobs are skipped.

To Reproduce Steps to reproduce the behavior:

1. Create the require-pod-probes policy
2. Create the following example job which starts a pod without livenessProbe and readinessProbe defined

apiVersion: batch/v1
kind: Job
metadata:
  name: test-probes-job
spec:
  template:
    spec:
      containers:
      - name: test-probes
        image: k8s.gcr.io/liveness
        args:
        - /server
      restartPolicy: Never

1. Check the events with kubectl get events --sort-by='{.lastTimestamp}' -w | grep validate-livenessProbe-readinessProbe
2. You will see

5s          Warning   PolicyViolation    clusterpolicy/require-pod-probes               Rule(s) 'validate-livenessProbe-readinessProbe' failed to apply on resource Pod/default/test-probes-job-6q2p9
5s          Warning   PolicyViolation    pod/test-probes-job-6q2p9                      Rule(s) 'validate-livenessProbe-readinessProbe' of policy 'require-pod-probes' failed to apply on the resource

Expected behavior

The policy is not applied on pods created by Jobs and Cronjobs and it should skip them.

Additional context

Sorry if this is not a bug and just our lack of understanding of how kyverno policy works.