Deployer Maturity: RGD Deletion

[frewilhelm]

Description

#172 introduces a basic implementation of a deployer using kro.

The new deployer will only CreateOrUpdate the passed RGDs.

However, if the resource containing the RGD is updated with the same RGD but a different RGD name, the current/applied RGD must be deleted before the new one is applied.

If the applied RGD is not deleted, it will still be reconciled but nothing will happen with that RGD as the name differs from the RGD from the resource.

TODOs:

• Check if there are already RGDs deployed in the cluster that are referenced by the controller
  • If so, check if the name differs
    • If so, delete the applied RGD
    • If not, update the applied RGD
  • If not, create the RGD

The above described behaviour is not ideal, but a first iteration step to a mature deployer. The ideal behaviour will be implemented by #196.

Done Criteria

• Code has been reviewed by other team members
• Analysis of existing tests (Unit and Integration)
• Unit Tests created for new code or existing Unit Tests updated
• Integration Test Suite updated (includes deletion of existing unnecessary Integration Test and/or creation of new ones if required)
• Successful demonstration in Review