When operator dependency resolution fails, the reasons for the failure appear in an Event. The Event's involvedObject is a Namespace (rather than a Subscription, for example), because dependency resolution considers everything within a single namespace at the same time. Also, since Events must reside in the same namespace as their involvedObject, and Namespace objects are cluster-scoped, these Events end up being created in the "default" namespace.

Users expect to be able to discover failure details from their existing resources. These details, or a reference to them, should be projected onto the status of all Subscriptions in the failing namespace.