EventSources for basic Kubernetes resources like Deployment, Pod, etc shouldn't have to be part of an Operator but should be provided by the SDK.
Case in point: DeploymentEventSource in the tomcat-sample.

This is not as easy however as moving that class into a new package in the operator-framework. The DeploymentEventSource makes assumptions about how the Deployment is connected to the Tomcat object. Those assumptions are partly encoded in the TomcatController as it is responsible for adding the right labels and ownerReferences to the newly created Deployment. So currently the DeploymentEventSource is tighly coupled to the TomcatController.

This all still feels like there should be a default implementation coming from the framework as it's pretty complicated and even though there are different ways one could implement the functionality it's

operator-framework#259

$upstream:259$