The invalid (not de-serializable) Custom Resource Should Not Crash the Operator

In case multiple versions in CRD are in place and no proper conversion hooks are set up, it could be the case that the controller will receive an invalid object (different and non-compatible resource that the controller manages). In this case the controller should wont be able to de-serialize the object. But should just log end ignore the error and the event, and proceed as normal.