feature: Allow for related resources to be cleaned up automatically after CR is deleted

[SimonTheLeg]

Feature Description

Currently related resources are not deleted if the CR is deleted. We did this intentionally to avoid any potential conflicts from deletions.

However it does make sense to offer this as additional functionality for use-cases, where users want to have the cleanup fully automated and are accepting the risk.

Proposed Solution

Proposed solution is to make this behavior configurable. Current behavior should still be the default (as it is less invasive), but if you want you can enable the automated cleanup.

I believe the best way would be to configure this on a PublishedResource Basis. So we could add a bool field relatedresourcecleanup which defaults to false. However if it is set to true, then the syncagent would delete any related resources once the original CR is deleted.

At this point in time I think there is no need to increase the granularity and define such a behavior on a per related resource basis.

Alternative Solutions

No response

Want to contribute?

• I would like to work on this issue.

Additional Context

No response

[BergCyrill]

Since the API-SyncAgent currently does not respect finalizers (see #115 ), I would suggest this feature should respect finalizers on related resources too.

[xrstf]

I think before we can implement this, we need to mak sure the agent is actually watching the related resources, so it notices the delete event and can process the finalizer.

[mirzakopic]

waiting on #118