Closed
Description
For example:
- user creates kafka stacklet
- kafka-op creates kafka listener (which is managed by kafka-op)
- list-op creates kafka listener service (which is managed by list-op), but propagates labels from the listener
- kafka-op sees its ownership labels on the listener service and tries to delete it, starting a tug of war with list-op
- list-op sees that the service was deleted, recreates it
- rinse, repeat, ad infinitum
Arguably, this is actually two separate bugs that should both be resolved separately:
delete_orphaned_resources
should also do a sanity check againstowner_references
before deleting- list-op should use its own
ClusterResources
, and overwrite the ownership labels inherited from the listener
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Done