Add resource limits to kyverno-hook-pre-delete and kyvenro-hook-post-upgrade pods
Feature Request
Why
In an effort to clean up our bigbang deployment and apply some best practices, we've started doing build evaluations looking for expected configuration. One policy we've implemented is that every workload should at a minimum have Resource Limits, no matter how big or small. This has worked for almost everything, but the kyverno-hook-pre-delete and kyverno-hook-post-upgrade pods.
Proposed Solution
Add/plumb a resource block for the post-install hook