We have run into the issue described in #260 a few times now, so were forced to rollback the reports-server implementation to the default reporting system in Kyverno.
In doing so, we discovered that simply deleting the resources (in our case a source in ArgoCD AppSet) results in the two apiservice updates from pre-delete-api-service-cleanup blocking the base configuration from returning to service. By manually, deleting the updated apiservice configs, we were able to restore our Kyverno instance back to the default reports configuration.
We have run into the issue described in #260 a few times now, so were forced to rollback the reports-server implementation to the default reporting system in Kyverno.
In doing so, we discovered that simply deleting the resources (in our case a source in ArgoCD AppSet) results in the two apiservice updates from pre-delete-api-service-cleanup blocking the base configuration from returning to service. By manually, deleting the updated apiservice configs, we were able to restore our Kyverno instance back to the default reports configuration.