[GitHub] [camel-k] dhirajsb commented on issue #889: Camel-K operator should clean up kits and kit builders after integrations are deleted

[GitBox <gi...@apache.org>]

dhirajsb commented on issue #889:
URL: https://github.com/apache/camel-k/issues/889#issuecomment-616307749


   There seems to be an underlying assumption that the user will run the same integration again and hence the kit needs to be kept around. 
   
   Doesn't that lead to the following:
   * Deleting an integration completely is a two step process, delete the integration then deleting the kit separately. 
   * If a user deletes an integration without knowing that kit has to be deleted separately, kits will start piling up in the background, since `kamel get` only lists integrations. 
   
   I think the integration lifecycle is kinda ambiguous, since running an integration both builds,  deploys and runs it, and there is no clean state transition to deleting an integration completely. 
   
   At a higher level, there is a disconnect from when an integration comes into existence (preferably in a vcs), to being run using `kamel`. 


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org