[BUG] Creating an incorrect custom resource may lead to metrics/logs flood

[s-vitaliy]

Description

If someone creates an incorrect object that cannot be parsed, and the issuer/validator instance is restarted it creates a lot of warning events. Not that this behavior can be reproduced only when the app is restarted.

If a broken object is created without restart, the app will issue a single warning and you may think that it's not a big deal. But it is.

Steps to reproduce the issue

1. Create a broken K8S object (e.g. without a requied field)
2. Restart the kube-rs informer
3. See a lot of warnings.

Describe the results you expected

Single warning per object.

System information

No response

[s-vitaliy]

P0 since we need to verify this behavior with kube-rs. Hipotetically, this can lead to massive service fault, but need to check

[s-vitaliy]

It is not an issue with kube, it's an issue with backoff settings