Description

Currently, Kyma controller handles all reconciliation tasks. As the complexity of the reconciliation logic increases, mixing both provisioning and deprovisioning together makes the business logic hard to maintain and read.

Typical Symptom: We can find many specific condition handling if GetDeletionTimestamp().IsZero() to control when the CR is under deletion, and even worse, the code must follow a specific order.

To improve clarity and simplify the logic, we can extract deletion logic into a separate service.

AC

• Implement a dedicated service for handling Kyma deprovisioning
  • Invoke this service when the Kyma's DeletionTimestamp is not zero
• Remove existing Kyma deprovisioning logic from the current Kyma controller