currently, we create a configmap after the kyverno policy is created
However, in the kyverno policy handling, the policy controller possibly tries to check if the trigger exists, and then initiates the mutation of the existing objects.
Currently, since the configmap is created after the kyverno policy status is set to ready, there is no way we can guarantee that the trigger (configmap) will be seen when the policy controller is checking the trigger on the kyverno policy
This theory was tested out by creating the trigger config map before applying the intent.
In this scenario, the mutate of an existing deployment happened after the intent was created.
The reason it fails to patch the deployment is :