-
Notifications
You must be signed in to change notification settings - Fork 32
feat: UseCase DeleteSkrCrds with instances for MT, MRM, Kyma #2896
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: feat/kyma-deletion-service
Are you sure you want to change the base?
feat: UseCase DeleteSkrCrds with instances for MT, MRM, Kyma #2896
Conversation
|
The only CRD we managed left at the SKR after this use case is the Kyma one. I was first planning on having a separate use case for this one but now thinking about it, actually I would merge them together. So |
How about we try with even further granularity and try with one usecase per CRD, with Kyma last so in the events we would also have this distinction. If it figures this is taking too many reconciliations until final deletion we can still combine usecases into one very easily. |

Description
Changes proposed in this pull request:
Related issue(s)