-
Notifications
You must be signed in to change notification settings - Fork 345
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
Camel-K operator should clean up kits and kit builders after integrations are deleted #889
Comments
Running |
It should certainly clean-up builder but kits need to be kept as they are needed to properly determine how and if new container images have to be built |
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:
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 |
…trollers to cleanup generated resources
An integration kit is by design not tight to a specific integration but can be reused by any other integration that requires the same set of dependencies or it can be used as base image for a subsequent build to reduce the amount of data transferred from/to the registry, that's why kits are not deleted along with integrations. |
One approach would be to implement a GC-like mechanism that would run periodically and remove the unreferenced kits, created since longer than a configurable period of time. Otherwise, we can add a |
There's actually a quite old issue: #254 |
…trollers to cleanup generated resources
This issue has been automatically marked as stale due to 90 days of inactivity. |
Now that adding a new integration creates a
camel-k-kit-*
andcamel-k-kit-*-builder
along with the integration pod itself, it seems there should be some clean up to remove those when the integration is deleted? I'm seeing the custom resource/integrationkits still hanging around after I remove the integrations.The text was updated successfully, but these errors were encountered: