Description of problem:

The current cloudevent sdk lacks support for garbage collection (GC) mechanisms similar to Kubernetes. For instance, when transporting manifestworks through cloudevents drivers, there's no automatic garbage collection process akin to Kubernetes. For instance, in cases of cascading deletion, where a manifestwork is associated with an owner reference, the manifestwork should ideally be deleted in the background when the owner is deleted. However, this functionality is absent in the current implementation.

We need to enhance the cloudevents sdk to include garbage collection capabilities, ensuring efficient resource management in cloudevents contexts.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

1.  
2.  
3. ...

Actual results:

Expected results:

Additional info: