Feature Description
Right now, if I delete an object in kcp with foreground cascading deletion this is not propagated
by the api-syncagent to the service cluster. It uses the default background cascading deletion to
delete the synced object.
It would be awesome if the api-syncagent could respect (at least) the foreground cascading
deletion, so the object remains visible in kcp until all dependent objects are deleted in
the service cluster (which the consumer might not even see in kcp).
Proposed Solution
When an object is deleted in kcp with foreground cascading deletion, the synced object
in the service cluster should also be deleted with foreground cascading deletion.
Alternative Solutions
No response
Want to contribute?
Additional Context
This was already briefly discussed in Slack: https://kubernetes.slack.com/archives/C021U8WSAFK/p1778672894076129
Feature Description
Right now, if I delete an object in kcp with foreground cascading deletion this is not propagated
by the api-syncagent to the service cluster. It uses the default background cascading deletion to
delete the synced object.
It would be awesome if the api-syncagent could respect (at least) the foreground cascading
deletion, so the object remains visible in kcp until all dependent objects are deleted in
the service cluster (which the consumer might not even see in kcp).
Proposed Solution
When an object is deleted in kcp with foreground cascading deletion, the synced object
in the service cluster should also be deleted with foreground cascading deletion.
Alternative Solutions
No response
Want to contribute?
Additional Context
This was already briefly discussed in Slack: https://kubernetes.slack.com/archives/C021U8WSAFK/p1778672894076129