Find a way to prevent users from deploying context aware policies without the relevant configuration.

[jvanz]

When a user deploy a context aware policy without the relevant context aware configuration, the policy starts to run but it fails on evaluation time. Which can broke resources deployment in the whole cluster.

The goal here is to research a good solution for this problem. Considering the safeguards Kubewarden stack already have, is it necessary to do some kind of validation before hand? Is there something else Kubewarden can do to avoid this issue?

Current safeguards:

• kwctl scaffold will generate the right yaml configuration, based on the policy metadata
• Rancher UI will generate the right yaml configureation, based on the metadata found on artifacthub

[jvanz]

This is a spin off of https://github.com/kubewarden/namespace-label-propagator-policy/issues/8

[jvanz]

During one of our dailies we decided that the issue should not happen after fixing the bug on UI. Furthermore, we have other safeguard in place to avoid this kind of problem.