Managing a previously unmanaged module

[c-pius]

Description

TBD

This problem may also become relevant here: #1545

Reasons

The user may want to handover the lifecycle management of a module to KLM.

Acceptance Criteria

TBD

Feature Testing

No response

Testing approach

No response

Attachments

No response

[lindnerby]

For Refinement:
Scenarios that potentially could be problematic or lead to unforeseen behavior which need to be handled:

1. The module has released several versions in the meantime that were "skipped" due to unmanaged mode. Maybe something breaks during the update. Example Scenario:
   • customer adds Keda in regular pointing to 1.0.0
     • Keda 1.0.0 module-manager creates a CR A
   • customer unmanages Keda
   • Keda regular gets updated to 1.1.0 which removes CR A
   • Keda regular get updated to 1.2.0 (code for removing CR A turned off as all installations were updated accordingly)
   • customer re-manages Keda
     • Keda updated to 1.2.0, CR A orphaned in the SKR
2. For some reason a resource has set a deletion timestamp and is stuck in the deletion process. May be problematic if we try to apply a resource that has a deletion timestamp.
3. The FieldManager problem. If a user has made SSA changes with the module in the meantime and are listed as the Field Manager. This could cause issues with further updates, especially if we want to remove fields from the resource.