[Ruinan Liu (ruinan-liu)]

Summary

Delete a Composition's inventory Secrets from the downstream cluster's kube-system namespace when the Composition is deleted while its Symphony is not being deleted.

Behavior

• Add cleanupInventory as a tombstone recovery operation selected by selectTombstoneRecoveryOperation.
• Run cleanup when the operator is enabled, the Composition is in scope and opted in (eno.azure.io/recovery-enabled: "true"), and it has a DeletionTimestamp.
• List Secrets by the Composition's eno.azure.io/inventory-lineage label and delete all of them, across every synthesis UUID and chunk. NotFound counts as deleted.
• Start as soon as deletion starts; do not wait for dependents, downstream resource deletion, or CurrentSynthesis.Reconciled.
• Retry list and delete errors through the controller's normal backoff while the Composition still exists.

Safety

• Keep inventory when the Composition has eno.azure.io/symphony-deleting: "true"; Symphony deletion orphans downstream resources.
• Delete only Secrets with this Composition's lineage label in downstream kube-system.
• No finalizer, no Composition status writes, and no downstream resource deletion.
• Deleting Compositions still bypass recovery and inventory recording.

Limitations and Scope

• Best effort: if the Composition disappears before cleanup succeeds, its inventory Secrets remain.
• General garbage collection of inventory for Compositions that are already gone remains separate work

[Ruinan Liu (ruinan-liu)]

Respond to comment